Moved here from that other place for good.
Let me rephrase that: "It was never ONLY about the code."
Let me rephrase that: "It was never ONLY about the code."
www.frank.computer/blog/2025/05...
www.frank.computer/blog/2025/05...
>>
>>
When code's being created at "LGTM-speed", there's trouble ahead.
codemanship.wordpress.com/2025/09/30/c...
When code's being created at "LGTM-speed", there's trouble ahead.
codemanship.wordpress.com/2025/09/30/c...
And you can tell by the elephant rolling its eyes.
And you can tell by the elephant rolling its eyes.
THE CREDULOUS PRESS: Fully Clothed Tesla Innovator Does It Again
THE CREDULOUS PRESS: Fully Clothed Tesla Innovator Does It Again
Shirer, William L. The Rise and Fall of the Third Reich (p. 237)
www.bbc.com/news/article...
Shirer, William L. The Rise and Fall of the Third Reich (p. 237)
If developers really were your bottleneck, throwing developers at a problem would actually have worked in the past 20 years
If developers really were your bottleneck, throwing developers at a problem would actually have worked in the past 20 years
Ah, those pesky, irresponsible developers...
Ah, those pesky, irresponsible developers...
It's not about generating bigger batches faster, but thinner slices validated sooner.
It's not about generating bigger batches faster, but thinner slices validated sooner.
Right.
#toc
Right.
#toc
TMALO for the shorthand.
TMALO for the shorthand.
Well, no.
The fact that there are bigger queues and inventory piling up in front of these activities now doesn't mean at all that the previous bottleneck was in the place >>>
Well, no.
The fact that there are bigger queues and inventory piling up in front of these activities now doesn't mean at all that the previous bottleneck was in the place >>>
Not at all.
Not at all.