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.
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.
I think the answer to this is lack of adoption.
Ok, but the comment thread is about people preferring Bluesky to Mastodon, hence my confusion.
Isn’t the format literally just Twitter?
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.
Ah, yes, because if you do a modicum of prevention, like wearing a mask, you’re obviously missing life and there’s definitely no way to keep up with the world unless you just completely give up on safety. No in-between, snort covid or become a social shut-in.
/s
Over my dead body.
Not sure the son would see it the same way…
FYI there’s a fully playable unofficial port for Jak 1 and 2, and they’re working on the 3rd one: https://opengoal.dev/
deleted by creator
I feel like I’d believe it if the headline was about John McAfee.
In my experience LLMs do absolutely terribly with writing unit tests.
IMO this perspective that we’re all just “reimplementing basic CRUD” applications is the reason why so many software projects fail.
Good abstractions are important for the code to be readable. An AbstractEventHandlerManager is probably not a good abstraction.
The original commenter said that their code was “generic with lot of interfaces and polymorphism” - it sounds like they chose abstractions which hindered maintainability and readability.
Is it possible that you just chose the wrong abstractions?
I do, and whether I have a good time depends on whether they have written their code well, of which the book’s suggestions are only one metric.
How do abstractions help with that? Can you tell, from the symptoms, which “level of abstraction” contains the bug? Or do you need to read through all six (or however many) “levels”, across multiple modules and functions, to find the error?
I usually start from the lowest abstraction, where the stack trace points me and don’t need to look at the rest, because my code is written well.
That’s not creepy or weird, that’s horrifying.