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

My experience is that implicity is a huge problem as it's too often taken for granted and precisely not valued. Only when you stop doing people realize that since Jeff is on long leave server aren't updated and we've been hacked or that Lucy quited and everything seem to crawl to a halt because she implicitly was doing housekeeping on the database. It might not have failed you yet but be sure the day it does there a good chance it will be spectacular.


These are all expected and desirable outcomes. Sometimes technical debt is not worth paying off until your hand is forced, like in these examples.

A large part of management is making the implicit explicit, and communicating the outcome of these efforts.

None of these examples have anything to do with refactoring code, specifically, and the challenges faced within that work.


The first sentence contradicts the other two and it contradicts the previous position where refactoring was done implicitly without anyone above in the org being aware of it.


See my last sentence. The OP listed examples of process failure, not refactoring.




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

Search: