←back to thread

Shift Left Is the Tip of the Iceberg

(semiengineering.com)

179 points yatrios | 1 comments | 19 Nov 24 14:06 UTC | HN request time: 0.2s | source

Show context

0xbadcafebee ◴[19 Nov 24 15:15 UTC] No.42184298[source]▶

>>42183561 (OP) #

For those not aware, Shift Left[1] is (at this point) an old term that was coined for a specific use case, but now refers to a general concept. The concept is that, if you do needed things earlier in a product cycle, it will end up reducing your expense and time in the long run, even if it seems like it's taking longer for you to "get somewhere" earlier on. I think this[2] article is a good no-nonsense explainer for "Why Shift Left?".

[1] https://en.wikipedia.org/wiki/Shift-left_testing [2] https://www.dynatrace.com/news/blog/what-is-shift-left-and-w...

replies(13): >>42185611 #>>42186878 #>>42187331 #>>42187375 #>>42187393 #>>42187419 #>>42187454 #>>42187463 #>>42187501 #>>42188834 #>>42192801 #>>42194403 #>>42207068 #

1. JohnFen ◴[21 Nov 24 18:19 UTC] No.42207068[source]▶

Thanks for the explanation.

I have always called this "front loading" and it's a concept that's been around for decades. Front loading almost always reduces development time and increases quality, but to many devs, it feels like time-wasting.