Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Sprints are nonsense unless they have gaps bewtween them, noone can sprint indefinitely

This is the crux of the nonsense. A high-level engineer can work around this but for the mass of ticket punchers, it just encourages non-thinking, risk aversion, and a lack of trust between themselves do the pressure of velocity charts, which translates into buggy code, mounting legacy blockers.

I know frontend engineers who didn't know what a finite state machine was, nevermind how it was implicit in their business code. For the mass of mediocre engineeers, sprints kill incentive to learn and become a better engineer; no is rewarding you.

Product doesn't care cause they're incentive structure is advesarial to Engineering push-back on tech debt, refactoring, etc. Sprints allow them to make sure their bonus is on time. Then Product people quit when BS mounts, another round of Product management shows up, and rinse, repeat.

I've seen this cycle happen three times in one org in just 5 years, the org where I started as a Junior.

And don't let DevOps also be working against sprints in a mediocre org

Sprints have, for most of the industry, not the Top 10% employers and what not, frankly regressed the industry.

Everyone stops working for the organization and starts trying to figure out how to make the organization work for them, from engineering to product to devops, etc. Good hiring is also a factor in what you'll get out of your employers, but sprints don't get you more at either rate.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: