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

> a challenge to secretly improve a codebase without anybody noticing

That is how it should be done in any case anyway. Improvements should get slowly rolled out without disturbing the users and the business.



> That is how it should be done in any case anyway.

Not exactly. IT management should be always telling people stuff like "did you notice that the integration with XYZ that never worked well stopped failing?" or "did you notice that we delivered those few last features at record time?" and explaining why.


That is assuming that things are failing. $20m/year with 3 people does not look like anything is failing to me.


That is assuming things are improving. If you aren't improving anything, then yeah, you don't have anything to say.




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

Search: