9 ms·
Shift Left Is the Tip of the Iceberg
- 0xbadcafebee 2y agoFor 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 https://en.wikipedia.org/wiki/Shift-left_testing [2] https://www.dynatrace.com/news/blog/what-is-shift-left-and-what-is-shift-right/ https://www.dynatrace.com/news/blog/what-is-shift-left-and-w...
- leoc 2y agoSo “shift left” is roughly equivalent to “tests first” or “TDD”?
- marcellus23 2y agoI would say tests first/TDD is a form of shifting left, but it can encompass more than that.
- 01HNNWZ0MV43FF 2y agoIt can also mean manual testing earlier. Valve credits playtesting early and playtesting often for their success with Half-Life, Half-Life 2, and other games.
- Fuzzwah 2y agoNot just when they play tested but how. Silently watching someone play, only taking notes. No debrief. Source: the week I spent in the Valve offices in 2005, having Valve staff playing our in development HL2 mod.
- CodeAndCuffs 2y agoWas it Dystopia, by chance?
- mehagar 2y agoMore broadly it includes moving activities that are normally performed at a later stage so that they are earlier in the process. The idea is that defects found later in the process are more costly.
- hitchstory 2y agoThat's just one example of it. Other examples: * Replacing automated tests with (quicker) type checking and running it on a git commit hook instead of CI. * Replacing slower tests with faster tests. * Running tests before merging a PR instead of after. * Replacing a suite of manual tests with automation tests. etc.
- 0xbadcafebee 2y agoOr, again more generally: - implementing security features earlier (DevSecOps) - implement tracing and metrics/analysis tools earlier, use them to test and debug apps earlier (as opposed to laptop-based solutions) - building the reliable production model earlier (don't start with a toy model on your laptop if you're gonna end up with an RDS instance in AWS; build the big production thing first, and use it early on) - add synthetic end-to-end tests early on The linked article is talking about Shift Left in the context of developing semiconductors, so you can see how it can be applied to anything. Just do the needed thing earlier, in order to iterate faster, improve quality, reduce cost, ship faster.
- skybrian 2y agoYes, it can be applied to anything, but might not pay off with software like it does with semiconductors? Better tests and more static analysis are useful, but teams will often work on making their releases faster and easier, iterating more frequently, and then testing some things in production. We don’t want our software to be too brittle, so it should tolerate more variation in performance. But with chip design, they can’t iterate that fast and performance is more important, so they are doing more design and testing before the expensive part, using increasingly elaborate simulations.
- js8 2y agoSo aside from automation (which also has tradeoffs), when you shift left, what gets shifted right?
- saynay 2y agoThe knowledge needed to do the 'shift-left' tasks. The downside of making your developers take on more tasks that used to be handled by someone further down the chain is they need to know how to do those tasks.
- crabbone 2y agoNo, not really. It's a concept from the bygone era, before X-as-a-service took over a lot of software categories. It was intended to minimize friction between the QA and the development teams at the time the product was handed to QA. If the product had multiple defects, incrementally discovered, it would have to travel back and forth between the QA and the developers, stalling the development of the next version and generally creating a lot of noise and inconvenience due to the surrounding bureaucracy. There's no need to write tests upfront for you to shift left. All shift left means is that testing happens during development. Whether you start by writing tests and then write the actual program or the other way around -- doesn't matter.
- coryrc 2y agoNo evidence most of the activities actually save money with modern ways of delivering software (or even ancient ways of delivering software; I looked back and the IBM study showing increasing costs for finding bugs later in the pipeline was actually made up data!)
- coryrc 2y agoTo be more specific, let's say I can write an e2e test on an actual pre-prod environment, or I can invest much development and ongoing maintenance to develop stub responses so that the test can run before submit in a partial system. How much is "shifting left" worth versus investing in speeding up the deployment pipeline and fast flag rollout and monitoring? Nobody I've worked with can ever quantify the ROI for elaborate take test environments, but somebody made an okr so there you go. Far be it we follow actual research done on modern software... http://dora.dev http://dora.dev
- cogman10 2y agoIn fact, in my experience, these elaborate test environments and procedures cripple products. I'm firmly of the opinion that if a test can't be run completely locally then it shouldn't be run. These test environments can be super fragile. They often rely on a symphony of teams ensuring everything is in a good state all the time. But, what happens more often than not, is one team somewhere deploys a broken version of their software to the test environment (because, of course they do) in order to run their fleet of e2e tests. That invariably ends up blowing up the rest of the org depending on that broken software and heaven help you if the person that deployed did it at 5pm and is gone on vacation. This rippling failure mode happens because it's easier to write e2e tests which depend on a functional environment than it is to write and maintain mock services and mock data. Yet the mock services and data are precisely what you need to ensure someone doesn't screw up the test environment in the first place.
- coryrc 2y agoThere are many reasons you want to be able to turn up your whole stack quickly; disaster recovery is just one of them. And if you can turn up your environment quickly then why not have multiple staging environments? You start with the most recent of yours and everyone else's prod version, then carrots combinations from there Obviously this is for large-scale systems and not small teams.
- deleted 2y ago[deleted]
- 98codes 2y agoWhat helped me finally remember "left of what, exactly" is to imagine a timeline, left to right. Shifting left is moving things earlier in that timeline.
- DeathArrow 2y agoDo the hard things first?
- Buttons840 2y agoDo the things that are hard and important first.
- hammock 2y agoSounds like the bottleneck concept from Goldratt’s The Goal
- infogulch 2y agoI'm familiar with both concepts and they don't seem related imo. Maybe if you applied bottleneck theory to process design in the abstract? Sorry I can't evaluate this comparison further, I must have run out of my quota for Abstract Reasoning Tokens today.
- hammock 2y ago"Shifting left" is like moving the fat kid on the hike to the front of the line
- bigs 2y agoSounds like a similar/parallel thought to the project management waterfall paradigm whereby the earlier you get things correct (left) the less costly it is in the long run or conversely if you have to go and re-do things later on (right) you’re in for a shock (either cost, time or quality).
- tromp 2y agoFunny how correct is not associated with right. The normal association is reflected in he Haskell Either datatype for describing computations that either run into some error (Left error) or run successfully producing a value (Right value).
- lolinder 2y agoThat's because the association isn't right or wrong, it's progressing or not progressing, deriving from reading order. A Left value typically halts computation there and returns something to the user, whereas a Right value allows you to move on. One nice side effect of tying the mnemonic to reading direction rather than homonyms is that it carries over across languages better (though still imperfectly).
- Centigonal 2y agoa sinister observation, dexterously phrased.
- brightball 2y agoI’ve come to the conclusion that Kent Beck got just about everything right with Extreme Programming. There’s just not a formal training industry out there pushing it so many more people are selling and invested in other approaches with a lot of warts.
- devjab 2y agoXP is almost the opposite or shift right, similar to how every other “agile” development form pushes the necessary work forward. I think it’s telling that none of the modern software design systems seem to have given us a world where our industry is capable of delivering software on time and within budget. They’ve been around for 20 years, places follow them religiously and still fail. Maybe everything about those concepts are just wrong? I mean, you can have people like Uncle Bob who’ll tell you that “you just got it wrong”. He’s also always correct in this, but if so many teams “get it wrong” then maybe things like clean, xp and so on simply suck?
- rusk 2y ago”a stitch in time saves nine” ”prevention is better than cure” [ante-] ”closing the stable door after the horse has bolted”
- polishdude20 2y agoSounds like the exact thing we never did at my previous employer. Just do the bare minimum to get it out the door and then fix it later.
- infotecht 2y agoShift Left is about doing more work earlier in a process for efficiency -- it sounds like you at your previous employer were shifting right instead?
- ajross 2y agoThat's an orthogonal concept. The idea of "shift left" is that you have work that needs to be done regardless (it's not an analysis of "bare minimum"), but tends strongly to be serialized for organizational reasons. And you find ways to parallelize the tasks. The classic example is driver development. No one, even today, sits down and writes e.g. a Linux driver until after first silicon has reached the software developers. Early software is all test stuff, and tends to be written to hardware specs and doesn't understand the way it'll be integrated. So inevitably your driver team can't deliver on time because they need to work around nonsense. And it feeds back. The nonsense currently being discovered by the driver folks doesn't get back to the hardware team in time to fix it, because they're already taping out the next version. So nonsense persists in version after version. Shift left is about trying to fix that by bringing the later stages of development on board earlier.
- cellular 2y agoEverywhere i worked we had drivers running well before silicon came back. We used simulators for hardware. Using parts of existing hardware when possible and hacked Microsoft sw emulation to behave as our hardware would. When the hardware came back, it was less than a day to get the driver running.
- SexyKitty17 2y ago[flagged]
- createaccount99 2y ago
- bloodyplonker22 2y agoI had management who were so enthused about "shift left" that we shifted far left and broke the shifter, or perhaps, mis-shifted. Now we spend too much time developing test plan and testing and arguing about PRD that we actually deliver more slowly than competitor by a lot.
- hinkley 2y agoAnother flavor of this I've encountered is people in the management chain who can only think about faults per time interval and not about faults per interaction. So you make a tool that prevents errors and speeds up a process, now people use it four times as much, and now they wonder why they're only seeing half as many faults instead of an order of magnitude less. We are humans. We cannot eliminate errors, we can only replace them with a smaller number of different errors. Or as in your case, a larger number of them.
- theGnuMe 2y agoExcept it doesn’t work. What does work is domain experience. You get this by iterating quickly.
- MintChipMonk 2y ago> 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. Isn't ignoring the early steps that could save time later also known as false economy? https://en.wikipedia.org/wiki/False_economy https://en.wikipedia.org/wiki/False_economy
- marcosdumay 2y agoIgnoring earlier steps is the basis of Agile. It's only a false economy if they are the correct steps. If it turns out that they are wrong, it's a very real one.
- JohnFen 2y agoThanks 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.
- hinkley 2y ago> Optimization strategies have shifted from simple power, performance, and area (PPA) metrics to system-level metrics, such as performance per watt. “If you go back into the 1990s, 2000s, the road map was very clear,” Tell me you work for Intel without telling me you work for Intel. > says Chris Auth, director of advanced technology programs at Intel Foundry. Yeah that’s what I thought. The breathlessness of Intel figuring out things that everyone else figured out twenty years ago doesn’t bode well for their future recovery. They will continue to be the laughing stock of the industry if they can’t find more self reflection than this. Whether this is their public facing or internal philosophy hardly matters. Over this sort of time frame most companies come to believe their own PR.
- talldayo 2y agoIntel has had a few bad years, but frankly I feel like they could fall a lot lower. They aren't as down bad as AMD was during the Bulldozer years, or Apple during the PowerPC years, or even Samsung's early Exynos chipsets. The absolute worst thing they've done in the past 5 years was fab on TSMC silicon, which half the industry is guilty of at this point. You can absolutely shoot your feet off trying to modernize too quickly. Intel will be the laughingstock if 18A never makes it to market and their CPU designs start losing in earnest to their competitors. But right now, in a relative sense, Intel isn't even down for the count.
- buildbot 2y agoIntel has failed pretty badly IMO. Fabbing at TSMC might actually have been a good idea, except that every other component of arrow like is problematic. Huge tile to tile latencies, special chiplets that are not reusable in any other design, removal of hyperthreading, etc etc. Intel’s last gen CPU is in general faster than the new gen due to all the various issues. And that’s just the current product! The last two gens are unreliable, quickly killing themselves with too high voltage and causing endless BSODs. The culture and methods of ex-Intel people at the management level is telling as well, from my experiences at my last job at least. (My opinions are my own, not my current employers & a lot of ex-Intel people are awesome!)
- zusammen 2y agoAs soon as I saw “shift left” I knew I wanted to double down.
- vardump 2y agoThis kind of joke might multiply…
- munchler 2y agoWay to manage up.
- globnomulous 2y agoBingo. I started reading the article and found it to be packed with jargon, buzz words, and the language of breathless prophecy and faddish hype. I couldn't hear the point of the article over the blasting sirens of my BS detectors, so I just stopped reading. Seriously, is there anything in the article worth the effort of slogging through all of that business-school/project-management shorthand/nonsense?
- deleted 2y ago[deleted]
- game_the0ry 2y agoIn my org [1], "shift left" means developers do more work sooner. So before we clearly clarify product requirements, we start the build early with assumptions that can change. Sometimes it works, sometimes it does not, which just means we end up net neutral. But an executive somewhere up the management chain can claim more productivity. Lame. [1] I work at a bank.
- Spivak 2y agoI think that's a myopic view. Getting something anything in the hands of your potential users that's even vaguely in the ball-park of a solution shaped thing gives you extremely valuable information both on what is actually needed and, to me more importantly, what you don't have to build at all. I consider it a success when an entire line of work is scrapped because after initial testing the users say they wouldn't use it. Depending on the project scope that could be 6-7 figures of dev time not wasted right there.
- game_the0ry 2y agoMuch of what you are saying does not apply to consumer banking. "Build fast and break things" works in big tech, but its a serious risk in financial services. That being said, we are being forced to "build faster and try not break things."
- massung 2y agoI’ve never been in banking, but I’ve been in games (AAA) and biotech most of my career. I agree with the previous commenter. It isn’t about breaking things out even moving fast (in my experience), but about getting “the juices flowing”. I’ve found that when there’s a request for some new tool or thing, people have a very difficult time defining [all] the real world needs. They know they need X, but don’t remember - or even realize - they also need Y, Z, etc. Or worse, many people have been conditioned through corporate culture that they can’t even ask for things that would make their lives easier. Getting something basic in someone’s hands quickly with the desire of creating a loop of feedback, feature, feedback, … gets the end user more focused and engaged with the final product, which gives the engineers more focused requirements. I’ve found it also gives the engineers the opportunity to make suggestions and get more invested.
- from-nibly 2y agoIn software shifting left often also means putting more tasks into the hands of the person with the most context, aka, moving deployment from ops to developers. The main benefits you get from this is reduced context switching, increased information retention, increased ownership. But it has to go with tooling, and process that enables that. If you have a really long deployment process where devs can get distracted then they will lose context switching between tasks. If you make every Dev a one man army that has to do everything on their own you won't be able to ship anything and your infra will be a disjointed mess. They key thing is reducing toil, and increasing decision making power within a single team/person. From the sound of the article they might be just squishing two teams together? What's the advancement that made the two steps be able to happen at the same time?
- yoelhacks 2y agoThe shift right parts of the article are more interesting...
- lizknope 2y agoI'm in chip design and our VP's and C level execs have been saying "shift left" for the last year. Every time someone in the Q&A asks "What does shift left mean?" No one talks this way except for executives. We just joke "The left shift key isn't working on my keyboard" or some other nonsense.
- peanut-walrus 2y agoCan we please stop naming things after directions? I don't want to shift left/right/up/down and my data center has no north/south/east/west. Just say what you actually want to say without obfuscating.
- sophacles 2y agoI guarantee your data center has a north, south, east and west. I'm willing to bet that the north, south, east and west of your data center are the same as the north, south, east and west of the office I'm sitting in!
- addaon 2y ago> I guarantee your data center has a north, south, east and west. Difficulty: Poster runs Santa Claus's data center.
- Cpoll 2y ago> I'm willing to bet that the north, south, east and west of your data center are the same as the north, south, east and west of the office I'm sitting in! Not really. Magnetic declination is a thing. And besides, unless we're standing in the same place, my "north" is not your "north." If you want to fight me on that I'll meet you one degree due north.
- sitkack 2y agoChip design is full of ridiculous terms that don't mean what they say. You kinda just have to go with it, or it will drive you mad.
- CGamesPlay 2y agoYeah, should be "shift inline-start", for better i18n.
- bsder 2y agoImagine the world of software if your editor, compiler, virtual machine, etc. each cost a million dollars a year per programmer. This is reality in VLSI CAD. Now you understand why everything in hardware engineering is stupidly dysfunctional. We don't need "shift left". We need tools that don't cost a megabuck.
- sitkack 2y agoThen stop paying Cadence and Synopsys to screw you over. Fund and support open source tools, demand open PDKs.
- adrian_b 2y agoThe reason why Cadence and Synopsys do not have concurrence is that there are no open PDKs for modern technologies. The existing open PDKs are for technologies from 20 years ago. If TSMC, Intel, Samsung, or even Global Foundries or other second tier foundry would publish the design rules for their manufacturing processes and specifications of the formats for the product documentation that they must receive from a customer, it would be easy to make something better than the overpriced commercial tools. I have used for many years the tools provided by Cadence, Mentor and Synopsys, so I know with certainty that it would be easy to improve on them if only one would have access to the documents kept secret by TSMC and the like. This collusion of the foundries with the EDA vendors that eliminates the competition from the EDA market does not make much sense. Normally better and cheaper design tools should only bring more customers to the foundries, so I do not understand what do they gain from the status quo. (Unless they fear that public documentation could make them vulnerable to litigation from patent trolls.) Fear of competition in the foundry market cannot be the reason for secret design rules. There is negligible competition in the foundry market and the most dangerous competitor of TSMC is Intel. Yet TSMC makes now chips for Intel, so the Intel designers have seen much of the TSMC design rules and they could chat about them with their buddies from the Intel foundry division. So TSMC must not give great importance in keeping the design rules secret from direct competitors. Therefore they must keep the rules secret mainly for other parties, but I cannot guess who are those.
- noisy_boy 2y agoAka A stitch in time saves nine. We seem to be hell bent on ignoring age old common sense repeatedly in our work while simultaneously inventing new names for them. Wonder why? Money? Survival? Personal ambition? These concepts are not worth the paper you wipe your backside with unless you have a manager and a team that cares.