2 ms·
I'm not sure that having your expensive software engineers not work 2.4 days a year is very palatable
by YawningAngel 2mo ago
I'm not sure that having your expensive software engineers not work 2.4 days a year is very palatable
- Dylan16807 2mo agoThey have other stuff to do that's not bottlenecked on push/pull/CI. 1% github downtime should reduce productivity by a lot less than 1%.
- himata4113 2mo agoThere are n services and n tasks, the chances of overlap are minimal. In most cases people take a much needed break during downtime.
- dmurray 2mo agoActually I think it's better if everything fails at once and everyone can take the day off (thanks, AWS!). Having your CI fail one day and your package repository the next might well cost you two days of productivity.
- vel0city 2mo agoI fully agree with this take. We need to ensure we get every hour of work from our expensive engineers. This is why we got rid of coffee machines and bathrooms and moved to intravenous caffeine and other fluid drips and catheters. We cannot afford to lose productivity.
- dmurray 2mo agoThey already don't work for 130+ days of holidays, weekends, vacations and sick leave. What's another two days? Probably I already ask them to spend 2+ days attending HR or compliance training or listening to senior management tell them about sales targets. But the point is, that 1% extra productivity requires the sometimes staggering cost of making the software 10x or 100x more reliable.
- snapcaster 2mo agoIf your margin for error is this tight something is fundamentally broken in your business