one of the big dilemmas was what to do with all the carefully crafted Use Case specifications that were getting less and less relevant as the real user feedback came in https://blog.crisp.se/2016/01/25/henrikkniberg/making-sense-of-mvp
Agile, YAGNI, Smaller Steps, Bikes and Automobiles... https://agileotter.blogspot.com/2026/05/agile-yagni-smaller-steps-bikes-and.html
The problem with the mental model is that it’s inside a human head. It’s a volatile place. We’re prone to distraction, forgetting, interruption, and depletion. The more we rely upon the persistence of our thought and memory, the more prone we are to a loss of context and having to start over again. https://www.industriallogic.com/blog/work-to-be-interruptible/
There are few effects more feared than the pooshoe effect: where you step in the poo, and it sticks to your shoe.
For example:
Someone needs something done in ADO or Jira, but you are afraid that once you have done a ticket administration task (as a favor), that will be your job for the rest of your employment.
It's a skill you don't mind having, but it's one of the least desired forms of employment you can imagine.
To you, the ticket systems administration is the poo.
If you step in it, will you stink of it forever?
You fear.
You think twice.
It's happened before...
Will this be the end of enjoying your job?
And that’s not all! Here’s the full programme (more: https://socratesuk.org/training_day.html):
* @emilybache - Controlling Legacy Code with Approval Tests
* @lisihocke - Secure development lifecycle
* Gemma Cameron - Bringing User Stories to Life (@ruby_gem)
* @claresudbery - Using TDD to get Better Results from LLMs/AI
* Jon Jagger - TDD with Cyber-dojo
* Duncan McGregor & @natpryce - Extreme Refactoring
* Tim Ottinger - Value Stream Mapping (@tottinge)
It's so weird when you are listening to people online in a seminar or podcast, and they're singing your song, and then they start to use your own figures of speech and metaphors, and even stories.
I mean, it's flattering to be sure, but it's like looking into a funhouse mirror: it's you, but it's not you.
I'm always concerned about handoffs, because where there is a handoff there is a queue, and where the queue reader is busy it results in a wait (and, of course, every item in the queue waits on the one before it).
So with Platform and Complicated Subsystem teams, how are you handling Stream Aligned teams' dependencies? How are you avoiding queuing and waiting for those dependent teams?
Curious if you are loaning out your people to teams to avoid handoffs, bringing their people into your teams' code to expedite, leaving the code fully open to external changes (with review and refactoring to follow), or just dealing with queues and waits.
Article begins "you shouldn't assign every ticket to a developer at sprint planning"
I'm thinking that this is going to be good - people pick up work as they become free, work in teams, and self-organize to complete work, right?
No: They argue that every developer should assign themselves a full load of tickets at sprint planning time.
Same problem: no room for collaboration, only individual action. Same queues, waits, dependencies. Still scatter-gather. Sigh.
So why? "So they FEEL more empowered."
Well, that's great for changing the optics without making a difference.
Lewin's equation is that behaviour is a function of the person and their environment. A common well-intentioned error is to focus only on the individual or only on their environment/system.
Both shape behaviour. Both have to. This suggests that you needn't be exactly the same (in behavior) at home and at work.
Be at work at work. Be at home at home.
Be you in both contexts, but be you in that context, not context-free you.
How often do you go to read the latest news on some AI stuff and it's NOT really a product ad or press release disguised as news ?
When is the last time you saw people actually planning in a planning meeting? All we see is the un-teaming of team members.
https://agileotter.blogspot.com/2026/02/do-you-even-plan-bro.html
Adventures imply challenges. No challenge? No adventure.
You know I like continuous anything better than episodic anything when it comes to coding. I don't want quality and security scans to happen after I think I'm done, but while I'm coding (why make bad code now and fix it later?).
So I want to know how you do continuous security checking while coding. What IDEs and plugins are you using, and do you background-scan while coding? What git hooks help you stay on top of it?
The magnitude of the story point estimate didn’t relate so much to the magnitude of the actual effort, but rather to the variation!
Where the estimate was small, the actuals were also small. That seems reasonable. Sometimes the 8-point stories were do ne faster than 2-point stories. Sometimes a 5-point story “blew up” and took twice as long as some 13 point stories.
An astute manager once took me aside and showed me a scatter graph of estimates (in story points) to actuals (in days).
Today marks 7 months of unemployment and I am very much down to the wire.
I am a full-stack & backend web developer, fluent in TypeScript, with experience building data-focused applications and both SQLite and Postrges databases.
I’m located in the northeast United States and have experience working and successfully collaborating with small, remote teams.
Boosts are appreciated. 🙏
#FediHire #webdev #typescript #backenddevelopment #fullstackdevelopment
The commentators say that when/if the E files show that DJT has committed repeated statutory rape with trafficked underage girls, he won't lose any supporters - none.
The prediction is that they'll all be okay with it and may even double down on their support for him.
This is the weirdest timeline of all.
Agentic AI and Security https://martinfowler.com/articles/agentic-ai-security.html
