Skip to content
loading...

re: The ONE chart every developer MUST understand VIEW POST

TOP OF THREAD FULL DISCUSSION
re: I'd agree with you if that were true but it's not. I chose to focus this post narrowly because it's such a big topic and it seemed like a good id...
 

I'd be shocked if you found your team is more efficient/economically productive if you focused less on defect prevention, pretest defect removal

Whoa there... I never said that, I said this write-up focused on a single keystone.

I did not state if it was wrong or right, just that the article itself doesn't provide dev teams the tools to reduce.

FWIW it was merely a call out to think about action items, not down your work or the concept of the article.

I think other works such as boringtechnology.club/ offer more clearly actionable alternatives which focus.

Apologies, Lewis. I didn't mean to put words in your mouth. It's easy to misinterpret blog comments.

I read your link and I agree with the author's conclusions on the benefits and costs of adding technologies to your stack. But I'm not sure how that relates to the topic of my post. Can you help me understand the connection?

code of conduct - report abuse