4 ms·
> I think it's overly reductive to say that the only purpose a company has is to make money. Yes, but also no. It's a simplification that is amazingly accurate
by Hermitian909 3y ago
> I think it's overly reductive to say that the only purpose a company has is to make money.
Yes, but also no. It's a simplification that is amazingly accurate, it does help to think of different companies as thinking about money on shorter or longer timespans.
As someone working in big tech, I have to say that for certain features I would much rather ship the right 10,000 lines in 6 months than 100,000 lines of the kind of wrong thing. The cost of being even a little wrong at the scale my company operates at is eye-watering.
We had two teams do a bit of what you describe over the course of six months, shipped a lot without building much alignment. We are going to live with the cost of those decisions for a minimum of 5 years.
The lower bound of the cost of working around their mistakes right now is equivalent to... 80 engineer years maybe? Because now we have customers who rely on some insane functionality they built that we are contractually obligated to support (and spiritually want to maintain good faith) and it will infect a bunch of other systems that will now have to integrate with their choices and take on that tech debt.
- YZF 3y agoAbsolutely. But I think it's still worth talking about productivity in the sense of how much are you investing for the additional value you're generating. In the context of this discussion and your comment, wouldn't it be better if those teams were aligned and productive? Is that just not possible in large orgs/software or is it just poor management?
- Hermitian909 3y agoI think it's just unusual to have enough information to be able to plan up front. There are two aspects: 1. Do we have all the information to make the right product decisions now? 2. Do we have all the information to scope all the technical work? Both are unusual and the second requires the first. It's not that it never happens (A nearby team in my org did it over the last six months) but this has become harder to achieve as the complexity of software has increased.