Slowing us down from what?

In the context of many other measures I think speed is an important measure. Maybe even the key measure. I’ve even written a blog post entitled “reading code is an anti-pattern.”

But if the metric is, slowing us down from having more lines in production then the answer is unequivocally yes.

If the answer is providing customer value, or having a sustainable engineering culture. Then I’m not so sure. I’m not saying I believe the opposite, but it feels like excessively optimizing on the wrong thing.

Ultimately I think this asks the wrong question, I think most other surrounding questions is the right one which is - how do you safely and quickly deploy the right code to production that delivers customer value.

I think that will continue going forward involve doing so in an automated fashion, but then the right question isn’t, “should we stop reading code”. But something like “what is the right way to ship intent to production”

Because if you do the first without the second…

▲

rstagi 8 hours ago | parent | next [-]

Yes I meant delivering value ofc, and I love the framing you propose, so my question is: are we already at the point where we could go safely faster, if we didn’t look at the code?

	▲	mikgp 7 hours ago \| parent [-]
		I think it’s a maturity model question, and an individual ability question. And maybe an industry tooling question. Individual ability? Newer engineers should read and write more code than experienced engineers. Maturity model? Teams with better access to objective specifications can read less code than teams without it. Teams with more experience with building loops and validation frameworks the same. Industry tooling? I think we need more work on the spec driven development front. Some set of standards as to how we define contracts that LLMs can operate against that are more deterministic.

▲

verdverm 8 hours ago | parent | prev [-]

I see significant decline in product quality this year among those companies most pilled (Ant, Goog, Msft, etc...). I had been commenting that Atlassian turned a page and Jira was running quite well, but this year... their internal push on Rovo has shown in their product, and their new `twg` CLI is some real slop where help text doesn't match the code.