4 ms·
This is just a new name for practices that have been in place for at least twenty years on decent projects. See fail fast, test early, small features, frequent
by swader999 3y ago
This is just a new name for practices that have been in place for at least twenty years on decent projects. See fail fast, test early, small features, frequent early feedback, anti-pipeline pattern...
- repelsteeltje 3y agoAnd it isn't even new. I think I heard the term at least 5 years, and I don't work in a particularly fast moving area of software development.
- swatcoder 3y agoBecause we still have no licensing body in software engineering (and I like that), the exponential growth of hiring during industry booms means that many teams are working with very thin access to historical knowledge because there are zero or few “old timers” around to convey past technique. The new generation inevitably reinvents practices and sometimes resurfaces them through independent archaeology, and so there’s a lot of cyclical repetition of both successes and failures. There’s also sometimes lucky innovations when old ideas get aired out in a new context and yield different results than in the past. If you’ve been around for a while, it’s easy to call out these repetitions and it can be satisfying to do so. But at the same time, it often means that the new generation is finally catching up on things that nobody’s been around to teach them. That’s something worth celebrating, not diminishing.
- woleium 3y agoWell said :)
- unlikelytomato 3y agoAfter so many times being the youngster advocating for things like this to the 20-30 year experience crowd, I am not sure I agree that age or experience are really major factors in this context.
- gustavus 3y agoYa, after a while in the field I noticed that Xtreme Programming, Agile, DevOps, and now Shift Left, and most other ideas are all just describing the exact same thing. Be flexible in your work, set up your processes to be able to deliver quickly so you can adjust quickly. I was puzzled why it seemed we were learning the same lessons in an industry over and over again, and why we kept giving new names to things that we're already existing. Then I received enlightenment when I realized that consultants that were selling agile previously were now selling DevOps. The reason they keep changing the name is because it allows consultants to come in and charge you more money to tell you to do the same things management bungled the last 3 times, because the problem isn't with the business processes it's with the idiots running the company. Or to quote Scott Adams "If you notice a lot of focus on process improvement at your business that's a sign all the smart people have left and management is trying to figure out a process simple enough for the idiots left."
- recroad 3y agoWhat’s anti-pipeline?
- swader999 3y agoSee here, well worth the read, it's properly named: Pipeline Anti-Pattern. https://www.leadinganswers.com/2007/06/the_pipelining_.html https://www.leadinganswers.com/2007/06/the_pipelining_.html
- danielmarkbruce 3y agoLeaving a top class engineering shop for a ... not top class one is one hell of an experience. So many words/phrases for things that shouldn't need a phrase.
- swader999 3y agoSometimes that works if you get to call the shots...