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

It doesn’t though. I’ve left entire knowledge bases and bulletproof tools behind and haven’t looked back. Constant maintenance is a sign of shitty design. A hallmark of craftsmanship is leaving a supportable low maintenance environment in your wake - most people’s jobs exist in a world of shitty products and the maintenance environment around them. Linus Torvalds or Ray Eames could live wherever the fuck they wanted and their impact to the “backbone” of the world would still be immeasurable.


> Constant maintenance is a sign of shitty design. A hallmark of craftsmanship is leaving a supportable low maintenance environment in your wake

This rings true to me; I am no amazing programmer but things I have built (which managers complained took a bit too long) have just chugged along; I have almost never received a call about something broke badly or had major rollbacks etc. My longest record is a program I built 19 years ago which is still in use.


I had a role developing systems of increasing complexity of hardware, software, and interfaces and my mantra / threshold for development was always “no phone calls”. I sought to make a project robust enough to support like any other by on-site and field staff and direct my attention to the next challenge.

19 years is incredible! Congratulations on a job well done for nearly a quarter century!




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

Search: