Except "mass" is not useful by itself. It's not a chair factory where more people equals faster delivery, just like 9 women won't deliver a baby in a month. I wish companies understood this.

Are you complaining that older versions of Java don't have the features of newer versions of Java...?

For me, as primarily a backend dev, the argument was that it's a framework, unlike React, so you get an everything-in-one solution which is quite easy to setup and use.

Given that Google still hasn't killed this one yet, it's also a mature platform with plenty of articles online on how to use it.

IIRC the license was also better than React's, at least last time I checked.

Not sure on what the landscape looks like today, but when I was making the choice, the internet didn't seem to consider other solutions to be competitive with either React or Angular.

Over my dead body.

FYI there's a fully playable unofficial port for Jak 1 and 2, and they're working on the 3rd one: https://opengoal.dev/

Is it possible that you just chose the wrong abstractions?

Comments should never be about what is being done. They should only ever be about why it is being done.

If you write your code like suggested in the book, you won't need to rely on possibly outdated comments to tell you what's going on.

Any comment about "what is being done" can be replaced with extracting the code in question to a separate, well-named method.

Fair point!

First part of the article sounds like what I'd expect.

The second part makes me wonder if this research was sponsored by some company which provides "Prompt Engineering" training.

I also have the Pro version, and I like it, with caveats.

First of all, the LEDs are waaay too bright. I had to change their brightness levels in the firmware, which was not the easiest as IIRC the code for that was not the best documented.

On the flipside, making changes to the firmware, compiling and uploading it to the keyboard is quite easy.

Secondly, the Bluetooth can be a bit buggy. Not only can the keyboard randomly refuse to connect (for which the fix is a button combo to forget the connection), the two halves themselves sometimes have trouble connecting.

Thankfully, that's a rare occurrence, even if still quite annoying.

The keyboard itself, however, is still quite comfortable for my tiny hands, is very customizable in terms of what key does what, and you can connect it directly to your PC via cable.

The last one also has a caveat, though, as there's currently no way for the two halves to talk via cable (though I think some people are working on that, at least for the pro version).

I needed something good for work, and I mostly got it. I'm planning to stick with this keyboard until it dies.

Oh, and I like that you can adjust the tenting, though I always use the highest setting.

This comment smells of outdated software development practices.

If you have separate developers for writing unit tests, and not every developer writing them as they code, something is already very wrong in your project.

Deployment and infra should also mostly be setup and forget, by which I mean general devops, like setting up CI and infrastructure-as-code. Using modern practices, which lean towards continuous deployment, releasing a feature should just be a matter of toggling a feature flag. Any dev can do this.

Finally, if your developers are 'code monkeys', you're not ready for a project of this scale.