Good primer on Python properties. Opens the door to lower level mechanisms in the language.

Very good interview. She really point out the main issues. Quite a lot of the current debate is poisoned by simplistic extrapolations based on sci-fi. This distracts everyone from the very real and present problems.

Definitely this. This is an interesting talk, most thing shouldn't be shiny. It's not about stagnating of course, but you should think more than twice before adding a new technology to your stack. Mastery is when you know everything that's wrong with a piece of tech, before that keep in mind the amount of unknown unknowns and the cost of exploiting something new.

This nicely goes in depth on the five domains to look at to know where you stand as a manager. Also proposes action to increase the impact. Good food for thought.

Interesting points in this article. The exact definition doesn't matter much. What really matters is the common understanding within a team of what technical debt is. It's also a good idea to be able to link it to actual money and business impacts.

It points out the security risk but it's mainly a good explanation on how Python loads modules.

Looks like a really neat tool for testing low level and kernel dependent details in a reproducible way.

Old article, still an interesting approach to making changes and looking for growth opportunities. There is value in trying not to frame everything as problems to solve.

Interesting article. This is a good introduction to the ActivityPub protocol. It also gives nice flies and pointers on how to dive deeper.

Interesting exploration on the performance of SSDs regarding write patterns. Turns out sequential IO is still a thing, just for a different reason than with good old HDDs.

Clearly inspiring... this project really went from dying to skyrocketing. I'd like to see more of those.

This clearly doesn't look as interesting as ActivityPub...

A good reminder that there is life outside of Scrum... I especially like the framing of Scrum as training wheels. When you learned biking you outgrew the training wheels, didn't you?

Looks like a promising way to reduce the training cost of large language models.

Neat, short and simple post highlighting the important traits of TDD.

Nice poster. It's harder to classify programming languages than it sounds. This one is interesting.

Looks like an interesting tool to try. History is an important part of the shell experience.

This is another way to approach the question of having slack in your schedule. This is necessary, and probably at scale in the organization (as implied by this article).

Even the giants are slowly moving back from microservices. DHH has a very cruel way to point it out, still that's true. Let's hope people realize the mistake it was in term of complexity.

This is indeed looking more and more like a viable and worthwhile option for web applications.