4 ms·
You make valid observations but you conflate issues. Continuous development is not a problem per se; overdevelopment is. Companies need to be able to say when s
by esafak 3y ago
You make valid observations but you conflate issues. Continuous development is not a problem per se; overdevelopment is. Companies need to be able to say when something is done, put on maintenance mode, and move on to something else. One problem that you did not mention is that business incentives can run counter to product demands; ticking more checkboxes just sells better with certain kinds of buyers. Many companies have not sown the seeds for new products to shift resources to; one trick ponies are the order of the day. So that would mean shedding staff, which looks bad for the company, and is bad for the workers' jobs :)
- bane 3y agoI don't really disagree with any of your points either. > one trick ponies are the order of the day. So that would mean shedding staff, which looks bad What I think I'm arguing is that most companies really don't need dedicated full-time staff in that way. Agency models work well in many industries that are built around one-trick ponies, which I'm arguing is what most development really is. In those industries there really isn't a negative connotation to ending a project, shipping it, saying goodbye and thanks for the hard work to the team who did it. If they did a good job and the activity was successful, many of them will likely be hired back for the next job anyways.