3 ms·
"It's a marathon, not a sprint". I've only ever heared this phrase working for a big corp during my first large incident response engagement. Having worked bot
by WhatsName 3y ago
"It's a marathon, not a sprint". I've only ever heared this phrase working for a big corp during my first large incident response engagement.
Having worked both at startups and large organizations, I can tell that there are two extremes and neither are healthy.
It seems like you got used to the constant crunch time that startups use to burn faster through their usually young human resources. From my experience, noone can sustain that pace without getting burned out or/and (willingly) compromising on their spouses and personal connections outside work.
Looking at the bigger picture you might realize that there are different point of views what progress means. In big corp it's usually about getting rid of/around obstacles, while startups focus on growth, happy VCs and other metrics that mean very little to a big corporate machine that by itself got enough intertia to keep moving even if it doesn't hit those metrics.
Conversely if your current business is running on billable hours. Finishing earlier and providing unrealistic client expectations might activly hurt your employer.
- sonicshadow 3y agoThen they proceed to call the samn things “sprints” and except us to do them back to back to no end
- michaelmior 3y agoA "sprint" when managed well, doesn't need to mean working tirelessly the entire period. One of the features of sprints is a way to avoid scope creep by imposing a deadline. I would argue that generally the more appropriate response to not meeting a sprint deadline is more often to cut scope than to insist than to insist devs put in extra hours.
- sonicshadow 3y agoWish that ever happened. We just add shit to our sprint and yell at devs when they are burned out.
- michaelmior 3y agoUnfortunately, that does of course that does happen a lot. My point was that I think working sprints doesn't necessarily mean overworking.