I recently figured out why "the Agile movement" no longer meet my needs. It has mostly transformed from focusing on playing the game to commentary about the game. That is, we've come to value the commentators over the players.

TIL that a “data lake” is just an S3 bucket stuffed choke full o’ good ol’ csv files

You know the target audience is members of the cult when nuanced comparisons could have been made and been favorable, but instead you went for over the top dumb.

Kubernetes is an Ancient Greek word meaning "More containers than customers."

It amazes me that the same people that consider “developers” fungible are upset when the resources consider them equally exchangeable. — Torbjörn Gyllebring (@drunkcod)

Hatten av för @drunkcod som blev första svensk någonsin att springa längre än 27 mil på 24 timmar. Grattis killen - du är jävligt dålig på att ge upp!

What happened to Agile Coaching? I’ve been in Agile for quite some time now What I see today doesn’t look anything like the Agile I got involved with I think it's time we talked about it

I'm getting really tired of getting told that theoretically the code that just ran in perfectly fine won't perform well enough... especially when I ran it on the worst case scenario.

Instead, solutions sold and accepted seem more uniform, more similar and shallow. We churn tools, frameworks, and styles at a more frantic pace than ever. But deep insights, measured tradeoffs, and engineering. They are as rare as ever. But we do love scaled ceremonies

When I started programming, it was a profession of geeks and nerds, an odd minority. Today, it's the most common job in Stockholm, the 8th most common in Sweden. The what, how, and who has changed as drastically, I'm sure. That's awesome, and it should imply more nuance.

I'm starting to believe that Software Peoples ideas about factories is more wrong than the idea of Software Factories

I wonder if Agile of 2 decades ago really "failed". Perhaps it's more accurate to think that the profession swelled and changed so much that the industrialization we see is simply an inevitable consequence.

This also applies to your "architecture", like it or not, understand it or not. It's there.

If priorities are what you actually do, most "software" organizations simply aren't.

I finally took some time to write about our way of working and how we use our board: https://t.co/CTcuyla8Jr - Thanks @laurilubi & @drunkcod, for pushing this to happen and giving valuable feedback

Nowhere in the laws of physics is it required that a commit, push, or PR can only be for a fully completed feature. Some people made that up, and it is likely not a good choice for your org.

I'm seeing #lascot Tweets. I'm getting sent pictures. And all I can say is: OH GOD I MISS YA'LL.

Metrics, measurement and guesstimates - you can use them to learn or you can fail at using them for control. Efficacy is deeply linked to perception, intent and what happens post measurement, when in doubt just remember to not do unto others...

DevOps engineer explaining why we need to use Kubernetes

Collaboration? In most cases it's more like cojabberation.

I find linear progression training fascinating. It begins so simple, so EASY. You just do 3 sets x 5 reps or whatever, and add 2.5 kg or 5 lb to the bar every time you succeed. 📈 At first...