It was never named for what teams *should* be doing, it was named after what businesses want teams to do. What do you mean, you can't sprint at a constant pace indefinitely?
@reschex
Engineering Director Making software delivery more enjoyable for those around me, using Agile and Lean principals, reducing waste and increasing flow & feedback. A Theory Y leader who believes in experimentation & learning over planning & execution.
It was never named for what teams *should* be doing, it was named after what businesses want teams to do. What do you mean, you can't sprint at a constant pace indefinitely?
I didnβt realise it was that easy to get you on a zoom call, I need to chance it more π«£π
But Jason, that means I need to think for myself and break domain specific problems down into a series of generic, LLM solvable, problems π€ain't nobody got time for that..
And while LinkedIn would like me to believe I'm doing it wrong, it doesn't feel that way.
Here we are, in the age of AI, where everybody is debating how to say 'Claude' 50 times a day.
Yet, I'm finding myself creating guideline documents for co-creation and micro-refactoring, rather than how to orchestrate more agents.
The Green Party isn't funded by mega-wealthy private donors pushing their own interests. It's funded by its rapidly-growing membership.
I highly recommend joining, maybe even donating a few coins, to help them get the message out that minority rule and Dickensian inequality aren't the only choice.
Great episode, I came |-| this close to saying "I'm bored" in a meeting today. Need to work up the courage..
Also, I'm not sure I can get over how weird it is to hear @dsquirrel.bsky.social swear π
A github screenshot showing a repo with the message "a user you've blocked has previous contributed to this repository"
PSA: If you block the `claude` user on GitHub, you'll get a warning every time you view a repo with that user in its commit history.
This allows you to, the moment you look at a repo, immediately adjust your expectations.
You may do so here: https://github.com/settings/blocked_users
Registration is live for CITCON:AI 2026 in Helsinki on the 22nd and 23rd of May. Get your ticket now!
Can't wait to discuss all things AI and how to make it useful with a great bunch of clever people.
citconf.com/helsinki2026...
I actually considered one of those when our cat was still alive π€· Bells did nothing for stopping her from bringing in all manner of wildlife, they are dangerous to cats unless they are attached to quick release collar, at which point you'll end up losing 2 collars/day.
Thanks @pauljulius.bsky.social - depending on what we find, I might propose a 'CI - 20 years later' or 'CI in the days of AI' topic at CITCON in Helsinki!
And itβs funny because, here I am, literally 20 years later, with a bunch of eager developers, testers, managers and SREs trying to improve our continuous integration practices and habits, reading essentially the source material, while looking forward to CITCON:AI 2026 π
Acknowledgement from the book continues integration, mentioning CITCON Chicago 2006
Funny.. my work book club picked a new book to read last week: Continues Integration - to my surprise, @pauljulius.bsky.social wrote the foreword. Not too surprising, I thought, the book has cruise control all over it.. and then I see this in the acknowledgments π
If it doesnβt stop raining soon, Iβll go drown myself.. on the lawn.
Just a reminder to check for your name in this list of books that OpenAI trained from. If your name is there, they probably owe you several thousand dollars.
OpenAI cried that if everyone eligible author files, the company will go bankrupt, so I'm alerting every author I have ever spoken to.
ha, love it. I guess thatβs why a lot of people have come to realise that a good name for bad scrum is waterscrumfall π€£
Just because you planned for weeks and then worked on it for months, doesnβt mean a) itβs not garbage, and b) it wonβt come back to you
(In fact, the longer you planned and the longer you worked on it behind closed doors, the more likely it is that youβll have to re-do a lot of it later)
And unless youβre delivering a fixed scope contract and retire straight after, all software development that delivers to users is iterative, whether you want it to be or not. You even get to pick the size/length of the iteration (whether you know that or not).
Here is another one, frequently deployed after a Demo: 'When can I give this to customers?' If the answer includes the word 'productionise', you're in a world of hurt.
Thin vertical slices is probably one of the most undervalued and difficult skills to learn in software engineering.
Same with making any (process) change and marking it as successful because it has been implemented.
have you read about Gas Town? steve-yegge.medium.com/welcome-to-g... Steve is at least up front about how many different control loops there are in place to keep the agents on track. I will admit I did not manage to read all of it, as I got too befuddled.
It hurt itself in its confusion!
I'm shaking things up in January.
1. Remote training bookings confirmed by Jan 31st are HALF PRICE. Save ££££ if you're planning training in the next few months.
2. All courses now have modules focused on applying code craft practices in AI-assisted wotshisface.
Details at codemanship.co.uk
Lego AT-ST Ultimate Collector Series Build
That was a lot of fun π€© #Lego #StarWars
Seriously, though. People saying that are telling so much on themselves and how they've always (quietly or not) looked at the engineering team.
Safari in #Zimbabwe #imire
If you asked me to characterise software development in its essence, I'd say it's a process of reducing uncertainty.
Otherwise known as "learning".
codemanship.wordpress.com/2025/11/28/w...
I've been trying, Jason. What's the secret to finding the right ones? I've been looking for two principal software engineers to work within and across a small number of teams, embedding everything you taught us. Finding someone who can describe, leave alone do TDD or refactoring is almost impossible
The problem was never 'not keeping it modular'. Oh it would have been so much easier if we had done DDD... I mean.. yes. But not doing DDD wasn't the problem.
Not doing the things that enable long-term sustainable development was the problem. Modularity and DDD are only a small part of that.