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).

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

Interesting ideas in there. It's not enough to pick up that something is off in a conversation. It's better to influence things to defuse the tension. Clearly not that easy to do, will require quite some practice.

And yet another set of open source models. This is really democratizing quickly.

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.

Truly open source models are pouring in. This is showing more transparency and I hope it will lead to better uses even though some of the concerns will stay true.