3 ms·
Deadlines are missed even for equivalent tasks previously done tasks, executed by a developer who is qualified and capable. Means even reproduction of pre-exist
by OneTimePetes 5y ago
Deadlines are missed even for equivalent tasks previously done tasks, executed by a developer who is qualified and capable. Means even reproduction of pre-existing work is hard with the code-base.
- goto11 5y agoThe problem is you never have "equivalent tasks". This is the blessing and curse of software development: You never have to do the same thing twice. Software tend to get more complex over time. Even if code quality is optimal, software will get more requirements added over time - especially if it is successful. If you allocate resources rationally, you will start by solving the "low hanging fruit" in the problem domain. So you cant really compare tasks at different stages in development.
- OneTimePetes 5y agoYou obviously have never been blessed with a truly horrific codebase. There are C-projects out there, were people do almost the same thing - twice. Like a endless papyrus scroll, and medieval scribes, modifying a copy and pasted atrocity for a month.Code this bad, usually never makes it to HN of course.
- goto11 5y agoIn any case, you can have the best code quality in the world and still miss deadlines if the deadlines are not realistic.