Dragan Stepanović
banner
dstepanovic.bsky.social
Dragan Stepanović
@dstepanovic.bsky.social
480 followers 130 following 270 posts
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.
Posts Media Videos Starter Packs
Reposted by Dragan Stepanović
But then I won't have the chance to practice my skills for reverse engineering understanding from the implicit code!
Sorry, it was a response to this LinkedIn post, which provides more context.
There's a feedback loop that feeds from making the changes to the quality of the mental model of the problem and domain

In doing the work, and if you listen carefully, you get to discover more about the domain and problem that feeds back into the way that you do the work.

2/2
One important questions to ask is: "What amount of domain insights are you missing out on by handing off creating the changes to the machine?".

Can you quantify that? :) Way more difficult, if not impossible, compared to "saved X hours creating this feature using AI".

1/2
So, the point is not reducing the cost per se. It's fixing the problem that the high cost of change pointed at, which in turns dissolves the problem of the high cost.

4/4
In a bunch of cases, the high cost of change serves a purpose. It points to a problem, addressing which reduces the cost that was pointing at it.

3/4
And my experience tells me that there are a lot of the latter ones that for lots of teams/orgs go under the radar, deferring addressing painful problems for a way longer time than they should.

2/4
I often ask myself if a technology, beside lowering the costs for which lowering the costs is beneficial, is also lowering the costs for which lowering the costs is detrimental.

1/4
I can notice the pattern, next talk is "Beyond UUIDs"
I heard there's this GOTO conference.
I think it's trying to popularize long forgotten tool of great software designers: GOTO statements.
You should try those as well.

I think SonarQube should also add it to one of their mandatory rules.
Amazing. That's already 5 Jira tickets done.
Hope you also tested some constructors and getters along the way.
That's all fine and dandy, but Nick did you test private methods?
Again those pesky reinforcing feedback loops and exponential behavior that humans are so good at understanding...
If you manage to do that, it's already a huge competitive advantage that is a blind spot for most, if not all, of your competitors.
Quantifying direct costs of multiple people working together is way easier than quantifying this one, but I'd bet my money that the latter is less expensive. And it's not the only one that you'd incur.

Don't get fooled by a bias of focusing only on the metrics that are easy to measure.
What are the costs and implications of a fragmented mental model of a domain across the team that you get as a result of people working in isolation?
Reposted by Dragan Stepanović
The only way to protect your future is by taxing the billionaires more.

At the @makethempay.bsky.social rally today.
The tyranny of economic growth obsession.
I heard wealth will trickle down one day, we just need to lower taxes again for them.
As American farmers would say, Trump is making Brazil great again. 🍿