Kissaki @ Kissaki @programming.dev

[@GitHub](https://github.com/Kissaki), [website](https://kcode.de/)

---

Read more

Posts

27

Comments

451

Joined

2 yr. ago

Sounds to me like the AI was programming using you instead of the other way around.

Did you copy and paste back and forth without learning or understanding anything? Or did you read and assess the results, and try to understand errors and issues?

no no no, this is the wrong way around

because sales and marketing sell it before it even exists

I know Julia. I used Julia. I moved away from Julia.

I'm on Nushell now for scripts, or C# for utils.

Mojo? Mojo games?

Mozilla has good introduction guides into web development https://developer.mozilla.org/en-US/docs/Learn

I would learn on the project, and use the official documentation to look up what it is, how it works, and how to solve what you want to do.

I'm surprised my not one of the biggest German cities is in there too. Very cool.

First half is a general introduction, second half is an introduction to their product Digma, which is limited to Java and IntelliJ.

Currently, Digma fully supports Java and IntelliJ, along with related frameworks such as Spring, Spring Boot, Dropwizard, and Micronaut. If you’re interested in other languages, you can find more information here.

Overall it feels shallow to me.

From what I see they didn't even support the claims they set out to present. They show a few screens of their tool, but never how that would "avoid breaking changes". The conclusion is incredibly generic. Feels like publicity/promotion and keywords content was the goal rather than actually sharing information. OP only posting their Digma content fits the impression of PR too.

How do you self-review while writing? What do you mean by that?

I see it as different phases of development, mindset, and focus. You inherently can't be in multiple at the same time.

1. Problem space and solution exploration - an iterative and at times experimental process to find and weigh solutions
2. Cleanup and self-review - document your findings, decision-making, exclusions, and weighing, verify your solution/changeset makes sense and is complete (to intended scope)
3. Reviews

It makes no sense to be thorough during experimental and iterative exploration. That'd be wasted effort.

After finding a solution, and writing it out, a self-review will make you take a systematic, verifying review mindset.

I wouldn’t do that, too much tunnel vision and biases.

Absolutely not. Self-reviews are very productive. I can confirm this from my own work and my colleagues, who also find it so.

You're of course free to vary the degree and depth of self-review, but tunnel vision and bias is definitely not overbearing and diminishing in those situations for us.

Someone else will of course see more, what you may not see due to tunnel vision. But that's besides the point.

No

Depends on the implementation. OP talked about potential of a CDN serving the shared resources. The instance servers wouldn't have to proxy the content. Which would allow caching and not duplicating content and transmission through multiple endpoints.

Yeah, I guess it's linear rather than exponential in growth. From an instance hoster point of view, it just never ends though, and not very predictable.

When they asked whether I use AI tools I chose yes, but the followup questions made it obvious they were talking about more specific query-based tools. So I went back and chose no instead.

What I use is Visual Studio IntelliCode. Which is free and local-only, and offers single-line-completions from context. It also offers completing repeated edits in more places.

It's an AI tool too, but nothing like the query-based chat-/text-interface or more complex AI tools - especially in regards to the questions that followed, which did not apply at all.

Mastodon is a Fediverse platform. Lemmy is too. Anyone can host their own Mastodon and Lemmy instances.

When a user uploads an image or video on Mastodon instance 1, and a user of Mastodon instance 2 is following them, that image or video is copied over to Mastodon instance 2 - because that's where that user resides.

This means content gets replicated and duplicated across every shared-network instance. Resulting in resilience, but also exponential, excessive storage needs.

OP is suggesting that media files should be shared across platform instances so that they don't get duplicated many times. This would significantly reduce storage and bandwidth needs and use for the platform instances themselves, offloading and centralizing media file concerns.

Aren't they teaching C in kindergarten?

The Windows integration will surely be awful for users. Windows 11 seems to be getting continuously messier, more convoluted, less focused, less accessible, less approachable, and less understandable. Adding AI and more online service integration won't make those pain points better. It'll make them worse.

The investments into technology and APIs like DirectML and "native" PyTorch will likely have a positive impact for developers making use of AI models.

Many of the other changes mentioned are unrelated to AI.

I supposed Dev Home is useful for big companies that need the setup, setting and workflow sharing, and the specialized features.

sudo seems like it could be a neat utility and addition. Git in File Explorer too - although it probably won't be useful to me personally. (TortoiseGit is already a great shell/File Explorer integration.)

Ironic that you don't share the pointers on what's expected to be checked with us.

An employer is unlikely to waste time on deep candidate analysis. If they see you as a public code contributor, it's an upside in activity, experience, and conversation starter, and discussion points for any interviews. If they look at your code, it won't be deep. I doubt they would go through the effort of correlating from a public coder profile (e.g. on GitHub) to a Lemmy profile and then look at their posts.

Once they're at the point where that would be a reasonable investment, they already know you personally and don't care about online content anymore.

Maybe some big companies use online analysis tools though.

Anyway, I know what I'm worth as a developer/an employed. I don't think I post that kind of divisive or sensitive stuff that does or possibly should be related to my employment and work. If they see it as such, then I'm fine with it not being a match.

I actually think the public nature could and should be upsides. Related to work or not.

Did you consider OP comment harassment?

The poster licensing to the platform is not the same as licensing to the public.

This instance programming.dev ToS declares:

2.2. By submitting, posting, or displaying user content on our services, you grant us a worldwide, non-exclusive, royalty-free license to use, reproduce, modify, adapt, publish, translate, distribute, and display such user content.

Distribution and displaying with attribution follows CC BY and SA. NC currently probably does - but may or may not (currently accepts donations).

The ToS only defines the license to distribute and display. It does not define how users and consumers of that distribution may or may not use the content.

So from this instance alone, there could be an argument of "the comment defines how it may be used".

But I'm not sure that holds given that federated distribution goes to other instances with different terms. For those that don't define how content may be consumed, it may be a reasonable argument. For those that define it in a conflicting manner, the ToS may override the content CC claim. Given the federated, distributed nature, given that you can reasonably expect such a conflict, there's a question of whether it holds in the first place if you can expect conflict invalidating it.

Either way, it's a convoluted mess, and incredibly noisy. Lemmy content has a language attribute. If there's a need for a license, it should be a metadata attribute in the same manner.

Is it gatekeeping if they voice their disapproval? Is any form of disapproval gatekeeping? Where is the line?

They didn't ask them to stop posting or participating. Wouldn't that be the line where it crosses to gatekeeping?

They asked them not to attach the CC notice. It didn't address their content.