Hacker News new | past | comments | ask | show | jobs | submit login

Actually you are ignoring the main argument here that people aren't perfect and that the risk of losing more time due to people getting distracted, reading slack, going on long coffee breaks, etc. is substantial and very real. You lose all that time; not just the build time. And having to wait is frustrating and demotivating. And let's face it, a 1 minute build is actually pretty sweet. I've been on teams where it is closer to 20. And worse. That really sucks the life out of you if you have to sit and wait for that to happen fifteen times in a day. People wasting hours per day waiting for builds, CI, etc. to happen is not cheap.



At my current place they have just replaced the build system.

If I want it deployed to the "higher" dev environments I have to watch it for 20 mins so that I can "approve" the override that my base image (that I have no control over) has security risks and I accept them.

If I want to deploy to production, I have to watch and approve the 20 min gatekeeper, them again at 40 mins, and then at 120 mins accept that I want a change ticket.

If I miss any of these then I have to restart the build process. This is an "agile" workplace.

Fuck everyone who claims they agile doesn't work, just stop calling this shit agile.


It's scaled agile my friend. Or was it scalable agile? Whatever.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

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

Search: