5 ms·
Isn't that a good thing? Each team has its own vacation policy that suits them, instead of some rules imposed on them by HR department.
by mamon 5y ago
Isn't that a good thing? Each team has its own vacation policy that suits them, instead of some rules imposed on them by HR department.
- geofft 5y agoAt that point, why have 1,200 people in a single company? Why not have each team hire each other team as contractors? (This isn't sarcasm, I actually do vaguely suspect the world would be a better place if we did this.)
- nikanj 5y agoIt's like microservices: the company, with all the downsides that come from higher transaction latencies between component parts. Economics of scale would also be lost, if you had to do all the book keeping, IRS reporting, etc etc for 120 companies of 10, instead of one company of 1200.
- geofft 5y agoWell, you could outsource those, right? Like isn't this basically the point of services like Stripe Atlas or Pilot - that it should be easier to run a company of 10, with almost all of those 10 people working on the actual product? In fact, outsourcing HR in particular is a well-established field - it's what companies like ADP do. Just like there's a happy ground between one massive monolith and multiple microservices per engineer, I think there's a happy ground between a 1200-person company and a bunch of sole proprietorships. It may not be 10; it might be 50. There are a huge number of <50-person companies in the world and they seem to be fine. In many cases, groups of these companies can execute faster than a 1200-person company can, because there's less internal hierarchy involved. (In much the same way that avoiding microservices doesn't mean you have no problems of interoperability, it just means they look different.)
- Donald 5y agoIt's also a good way to get slapped with lawsuits from decisions made by people who don't understand FMLA leave.
- valuearb 5y agoLegal can vet guidelines for the company, you don’t need a whole HR department to implant them, or anything.