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.
dandi8
joined 5 months ago
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?
FYI there's a fully playable unofficial port for Jak 1 and 2, and they're working on the 3rd one: https://opengoal.dev/
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.
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.
It's only as incomprehensible as you make it.
If there are 6 subfunctions, that means there's 6 levels of abstraction (assuming the method extraction was not done blindly), which further suggests that maybe they should actually be part of a different class (or classes). Why would you be interested in 6 levels of abstraction at once?
But we're arguing hypotheticals here. Of course you can make the method implementations a complete mess, the book cannot guarantee that the person applying the principles used their brain, as well.
You're nitpicking.
As it happens, it's just an example to illustrate specifically the "extract to method" issues the author had.
Of course, in a real world scenario we want to limit mutating state, so it's likely this method would return a Commission list, which would then be used by a Use Case class which persists it.
I'm fairly sure the advice about limiting mutating state is also in the book, though.
At the same time, you're likely going to have a void somewhere, because some use cases are only about mutatimg something (e.g. changing something in the database).
view more: next ›
That's not creepy or weird, that's horrifying.