3 ms·
> because it was built with current best practices, keeping the dependencies up to date and maintaining it would probably take multiple full time engineers / sw
by furyofantares 5y ago
> because it was built with current best practices, keeping the dependencies up to date and maintaining it would probably take multiple full time engineers / swe's at a FAANG.
Surely significantly less than one full time? But like 10% of an extra full time job that costs you money isn't a very good proposition
- hedora 5y agoEach dependency gets to choose when they break your service (they can have a zero day exploit that's only fixed in a compatibility breaking release, for example). You need two people if you want one to be able to go on vacation while you maintain a 24 hour SLA for security patches. You need a third because this sort of thing generates employee burn out once it is feature complete. You could try having it be 10% of one employee, but that employee would need to be a full stack expert from low level Linux stuff to JavaScript GUI junk. Good luck finding two people like that, then telling them they own ten feature complete services like this. The people that fit such a bill and have the personaility type to be happy in such a job are expensive and rare!
- crabmusket 5y ago> 24 hour SLA for security patches I think that's a significant step up from your earlier guess at "maintaining" the software. There's a big spectrum between "project has been shut down" and "round the clock SLA".