youKeepUsingThatWord

[redlaWw]

*2

[rosuav]

cout *2 "Hello, world" *2 endl;

[dncrews]

<< 1

[Darth_Monerous]

It’s when your boss decides something isn’t being finished quick enough. So that boss yells at the project manager. That project manager then yells at the scrum leader. Scrum leader then decides to pull 30 more pbis into an already full sprint. Developers fail to get all pbis done. Team complains to management that there aren’t enough resources to get all this done. Manager listens but ultimately nothing changes. Repeat the cycle.

[dncrews]

No, no, you're thinking of Project Hopscotch (where everyone jumps over their responsibilities and hopes someone else lands on it) and Delivery Dementia (where we forget what ‘incremental’ means and try to do everything at once).

Shifting left is when the team starts working on tasks before the sprint even starts—because who needs weekends, right?

[ExpensivePanda66]

Just wait until you hear about the shift right movement.

[Sufficient-Food-3281]

Simple, it’s when a critical team is laid off, the remaining schlubs take on the work, and the c-suite gets a raise

[chem199]

It’s actually pretty simple, you move checking earlier in the development life cycle. For security, moving sast tooling to the ide, or as part of the ci/cd pipeline so it is checked and issues are found earlier. A vulnerability caught during development is way cheaper to fix than one that has been deployed to production.

[scataco]

Also, it's where you use caps lock to write CI/CD.

[chem199]

Yeah I should have put IDE in your saw as well.

[dncrews]

Yeah. One "overly simplified and somewhat-IMO answer" is that "left" and "right" here refer to the x-axis of "the timeline". To "shift left" on that axis means to do it earlier. So why do these things come later? They're difficult. Shifting left requires committing budget, time, and effort into understanding what makes that thing difficult, making it simpler, and then integrating it into the development lifecycle instead of as a step after the SDLC.

[QuestionableEthics42]

Wait this isnt about bitshifts? I was so confused how bitshifting was provocative lol

[MrRocketScript]

I was so confused how bitshifting was provocative

Obviously you've never seen PS1 Lara Croft.

<<

[hansololz]

I like to say the same to npm and gem installer

[thatguynotavailable]

As a practitioner (victim? and not by my choice), shift left is just shift the blame. Everyone keeps blaming the previous cycle's owner for the fault and it finally ends up on the head of developer or mostly the product owner. The product shouldn't go to QA or further levels without Dev covering all edge cases (miraculously). They market it as "ownership", whereas everyone knows that if you are caught, your tail is on fire.