Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This approach is a trap.

Management need to know that this needs a rewrite, and a more capable team, and that persuing on aggressive roadmap while things are this bad is impossible.

If they say no, and you try to muddle your way through it anyway, you are setting yourself up to fail.

If they say yes, ask for the extra resources necessary to incrementally rewrite. I would bring in new resources to do this with modern approaches and leave the existing team to support the shrinking legacy codebase.



Why would the existing team stick around knowing their jobs would be slowly rewritten into oblivion by others?


Where else are they going to go if they prefer this mess?

Why would they need to be replaced if they’re ultimately convinced to enter the 21st century?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: