Long but interesting piece. There's indeed a lot to say about our relationships to tools in general and generative AI in particular. It's disheartening how it made obvious that collaborative initiatives are diminishing. In any case, ambivalence abounds in this text... for sure we can't trust the self-appointed stewards of the latest wave of such tools. The parallel with Spirited Away at the end of the article is very well chosen in my opinion. The context in which technologies are born and applied matters so much.
Looks like a nice resource to get started with graphics and 3D.
This is indeed interesting to see how the landscape evolved around error handling. There's clearly a tension between exceptions and the result types we've seen popping up everywhere now.
I think Rich Hickey hit that nail on the head.
Looks like Europe is finally waking up. It needs to pick up the pace now.
Nice little introduction in the fascinating world of very large binaries.
This is really fun tech. I need to find time to experiment with it.
Very comprehensive resource to make your own recommender model.
Indeed, social media even the fediverse isn't really about communication or community, it's about consuming content.
Careful of undefined behaviours. They can be reached fairly quickly. Especially in C++ and its initialisation maze.
A bit too unapologetic regarding Rust API choices for my taste. Still, it gives a good idea on how error handling works in Rust.
Early days for this little system tool. I really like the idea though.
I'm not sure I fully align with this piece. The core tenet of generic design advice vs concrete design advice makes sense though.
The situation about file locking is really complicated in the Unix systems family.
It's been written a while ago now... and it's admittedly still a mess. Be sure to read the addendum as well.
A good summary on the important rules to follow to debug something.
Interesting insights about pair programming.
Estimates are is always the weak spot in project management in my opinion. Story points are generally confusing and there are better ways.
The definition of ready can be a big help avoiding too many questions about stories as they are implemented. They should be clear before hand.
This is a very good resource on the different ways to split user stories.