this post was submitted on 02 Jan 2026
195 points (99.0% liked)
Programming
24365 readers
514 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't think that is fully the case, 300 hundred devs don't provide in a day what a dev provides in 300 days. Basically the coordination needed between those 300 devs require so much effort that they won't get done as much. I like the comparison with a pregnancy, with 9 women, you can't get one baby in a month. After 9 months you can end with 9 babies or so, but it still takes 9 months.
Having 300 devs is incredibly inefficient, with so many, many of those are just doing menial work. And surely there will be plenty doing less than they would do in a smaller team. The reason for such big teams I feel is double, one, high rotation of employees, like OP, the best ones see the shit show and leave. The worse ones that won't find another job easily remain, unhappy and even less efficient, so the company keeps hiring more. The other reason is, the more employees, the easier it is to get shitty unethical stuff done. Each dev provides a little bit of crap, so little that they might not see the impact or so that they won't feel like fighting it, but combined with everyone, it creates that shitshow.
That's not at all what I meant. Coordination of people is value added too, that totally counts into working hours.
That's the main spirit of what I tried to express. The more people to keep employed, the more ideas you need to justify your existence to the shareholders. The 300 devs aren't adding new features, aren't making your app faster, smaller, safer. The last 20 updates with "bugs fixed" in change logs? These bugs were bugs in A/B tests they are running on your device. They aren't adding any end-user facing value to the app or experience. They are adding new way of tracking, updating existing A/B tests for new remotely controlled flags, adding new A/B tests.
They are squeezing the profit margin from you. You're paying for it AND are the product.