3 ms·
I'm in my early 30s, so frequently called an older programmer and I've heard a lot of, "we don't have time". What I've been waking up to is that projects that
by sean2 9y ago
I'm in my early 30s, so frequently called an older programmer and I've heard a lot of, "we don't have time".
What I've been waking up to is that projects that estimate realistic budgets and time scales don't get funded. Everyone underbids knowing that the company/customer will continue to fund and extend deadlines for project after sinking so much effort into a buggy prototype, until the realistic estimate is reached and the product actually reflects all the "hidden"/"discovered" requirements (i.e. foreseen but not in the bid) including security, integration and test efforts.
What's weird is that everyone, customers included, seems to be in on this.
- gozur88 9y agoI think that's true, pretty much. But the downside is they force an inefficient development methodology on you as you try to make the imaginary deadline.
- imhoguy 9y agoWhat you describe is often the scenario of do-everything consulting sweat shop building tailored or customized solution from scratch based on a single customer requirements. Management often lacks business vision and technological path. Front sales and techical people are randomly assigned and switched between ad-hoc projects with varying industry domains and poor communication chanels. I think only debt slave or masochist stay in such places for longer. Age doesn't matter. I would rather look for more focused software product companies with stable teams.
- dennisgorelik 9y agoMost of new features are useless, so it does not matter that they are buggy. Only consistently useful features require bug-fixing. It is better to spend more time fixing bugs on few useful features after they implemented and tested by users, than spend time polishing all features (including useless features) up-front.