Very good review of the McKinsey paper about developer productivity. It not only highlights all the problems with it, it also makes suggestions to make a better paper next time.

Interesting approximations to get a feel of how much a cloud project will cost.

Unsurprisingly after people massively converged to two main closed source engines for their games, they start to be massively screwed over. Maybe it's time for them to finally turn to Free Software alternatives?

I'd take the more stack related side of this article with a pinch of salt. It seems a bit too specific to the company behind the story. The rest of the article rings true and spot on though.

And now the part two, with more warnings about what you measure. Also proposes a few ideas toward the end.

Excellent piece. Be careful what you measure. If you measure the wrong things people will game the system.

More thinking gets around the debate about tech debt. This is definitely welcome. Using more precise labels can indeed being clarity in conversations.

Clearly very much inspired by the science peer review system. Having experienced it, indeed I wish more business decisions would be made that way.

Very good advice. Don't waste time believing false business claims and trying to replicate them. Easier said than done though, most people don't have the privilege of insiders knowledge.

Remote work is clearly the best way for smaller companies to compete to attract talent. This greatly increases the size of the pool of potential hires.

Interesting and provoking thought... Indeed it's hard to build communities while also aiming for rapid and constant growth. There's no chance of having communities properly stabilize which leads to the tribalism and bad behavior we see on social media.

Interesting insights about the minutiae of the CTO role.

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.

Clearly a bit US centric but interesting trends nonetheless. We might see some of that reaching Europe (for good and for bad) fairly quickly. At least regarding hybrid work, flexible offices and more asynchronous communication, I've seen it globally spread already.

Nice overview of what it takes to increase your uptime. It can get expensive quickly. This is also a good reminder that it's not only about software, it's a lot about people and administrative constraints as well.

This was only a matter of time. It'll be interesting to see how this will unfold. Potentially it could turn into lawsuit cases being built up, it could also mean content producers get a cut down the line... of course could be both. Since FOSS code also ends up in training those models I'm even wondering if that could lead to money going back to the authors. We'll see where that goes.

Hm... interesting framework. Especially for me, I know I tend to be too verbose. Definitely something I'm willing to try.

OK, not a perfect article, I think there are a couple of blind spots in the reasoning (I doubt all the estimates were as systematically bloated as presented here). Still, it's another interesting account of the problems created by the cargo cult agile. It indeed seems to resonate with the fact that the tech sector is very hype driven. A lot of useless work then ensues.

When they changed their statutes it was the first sign... now it's clear all ethics went through the window. It's about fueling the hype to drive money home.

Interesting business model. Could be a new path for at least some maintainers to be sustainably funded. Still a lot of unknowns though... probably worth keeping an eye on it.