Dragan Stepanović
@dstepanovic.bsky.social
Trying hard not to think about small batches, bottlenecks, and systems. In the meantime: XP, ToC, Lean, Systems Thinking.
Moved here from that other place for good.
Moved here from that other place for good.
Sorry, it was a response to this LinkedIn post, which provides more context.
September 28, 2025 at 12:52 PM
Sorry, it was a response to this LinkedIn post, which provides more context.
Oh, I have another one! Available for pre-order!
July 9, 2025 at 2:19 PM
Oh, I have another one! Available for pre-order!
Or... Or... the team has mechanisms and practices in place to keep the cost of change low, so they are able to change code and adapt design just-in-time (emergent design), rather than trying to predict it when they have the least information about the code (design up front crystal ball gazing).
July 9, 2025 at 10:34 AM
Or... Or... the team has mechanisms and practices in place to keep the cost of change low, so they are able to change code and adapt design just-in-time (emergent design), rather than trying to predict it when they have the least information about the code (design up front crystal ball gazing).
New t-shirt in my store.
July 8, 2025 at 4:30 PM
New t-shirt in my store.
I'll just leave this here
July 6, 2025 at 6:15 PM
I'll just leave this here
The problem with the code that is not expressive, i.e. implicit, is not only readability per se.
It's that it's missing important domain concepts communicated in the code.
It's that it's missing important domain concepts communicated in the code.
June 17, 2025 at 5:40 PM
The problem with the code that is not expressive, i.e. implicit, is not only readability per se.
It's that it's missing important domain concepts communicated in the code.
It's that it's missing important domain concepts communicated in the code.
Just a regular reminder that predictability (and accuracy of estimates) goes down the drain as you overload the system with too much WIP?
How much WIP is too much WIP?
How much WIP is too much WIP?
June 17, 2025 at 6:57 AM
Just a regular reminder that predictability (and accuracy of estimates) goes down the drain as you overload the system with too much WIP?
How much WIP is too much WIP?
How much WIP is too much WIP?
Any time we say “it will be faster to do this one bigger step than the two small ones” we're missing an opportunity to change the system in a way that makes iterating cheaper.
It is faster to do one big step, _precisely_ because iterating in that system is expensive.
1/2
It is faster to do one big step, _precisely_ because iterating in that system is expensive.
1/2
March 4, 2025 at 10:57 AM
Any time we say “it will be faster to do this one bigger step than the two small ones” we're missing an opportunity to change the system in a way that makes iterating cheaper.
It is faster to do one big step, _precisely_ because iterating in that system is expensive.
1/2
It is faster to do one big step, _precisely_ because iterating in that system is expensive.
1/2
@github.com here's a feature idea:
Instead of “protecting” the main branch by preventing pushing straight to main, try inverse and prevent creating branches other than main.
Right, I know it doesn't sell, but that's what high-performing teams actually do.
Instead of “protecting” the main branch by preventing pushing straight to main, try inverse and prevent creating branches other than main.
Right, I know it doesn't sell, but that's what high-performing teams actually do.
February 18, 2025 at 1:11 PM
@github.com here's a feature idea:
Instead of “protecting” the main branch by preventing pushing straight to main, try inverse and prevent creating branches other than main.
Right, I know it doesn't sell, but that's what high-performing teams actually do.
Instead of “protecting” the main branch by preventing pushing straight to main, try inverse and prevent creating branches other than main.
Right, I know it doesn't sell, but that's what high-performing teams actually do.
Yes, I like that idea as well and it's my go-to method.
Leaning towards finding boundaries more based on empiricism than prediction (speculation).
At Ohio university they've let people walk on the grass to let the path patterns emerge and only after that paved those paths.
Leaning towards finding boundaries more based on empiricism than prediction (speculation).
At Ohio university they've let people walk on the grass to let the path patterns emerge and only after that paved those paths.
January 15, 2025 at 10:07 AM
Yes, I like that idea as well and it's my go-to method.
Leaning towards finding boundaries more based on empiricism than prediction (speculation).
At Ohio university they've let people walk on the grass to let the path patterns emerge and only after that paved those paths.
Leaning towards finding boundaries more based on empiricism than prediction (speculation).
At Ohio university they've let people walk on the grass to let the path patterns emerge and only after that paved those paths.
One of the big lessons of XP that often flies over people's heads is, don't focus on being fast.
Focus on going steady instead. Fast is a byproduct of steady.
Steady means you're minimizing rework and surprises by taking small steps and continuously invalidating assumptions along the way.
Focus on going steady instead. Fast is a byproduct of steady.
Steady means you're minimizing rework and surprises by taking small steps and continuously invalidating assumptions along the way.
May 2, 2024 at 7:47 PM
One of the big lessons of XP that often flies over people's heads is, don't focus on being fast.
Focus on going steady instead. Fast is a byproduct of steady.
Steady means you're minimizing rework and surprises by taking small steps and continuously invalidating assumptions along the way.
Focus on going steady instead. Fast is a byproduct of steady.
Steady means you're minimizing rework and surprises by taking small steps and continuously invalidating assumptions along the way.