4 ms·
The opposite of this would be "build it to walk away." It's not obvious that every project worth writing some custom software for is worth having a dedicated te
by skybrian 9y ago
The opposite of this would be "build it to walk away." It's not obvious that every project worth writing some custom software for is worth having a dedicated team working on it.
You need to think seriously about how to avoid changing dependencies, though. It's like planning an exercise in retrocomputing in advance.
- konschubert 9y ago1. Create a team to build a product and maintain it. 2. Once the product matures, and needs less attention, shrink the team or use the free capacity to build another product and add it to the team's portfolio. 3. If at any point in time the workload becomes to much, grow the team. 4. If the team gets too big, split it and distribute the product portfolio onto the two parts.
- mr_toad 9y agoIn my experience, most software development projects have been more like "build half of it, throw it over the wall, and make yourself scarce." Especially when consultants are involved. I have never seen traditional project management techniques successfully applied to software.
- pjmlp 9y agoI used to think like that, then I became a consultant and got to enjoy how companies whose main business is not at all related to IT do work. 100% of them don't care about code beauty or maintainability, just something that does what they need for their actual business, done in X days within Y euros/dollars/yang/.... So they get what they want, with the quality they are willing to pay for.
- tonyedgecombe 9y agoYes, it's hard to underestimate how poor most corporate software is.