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

To quote myself elsewhere, systems programming is first and foremost cost center, not value center, programming.

That explains why it's a bit dangerous for the programmer's career.



How would you explain performance improvements? Enabling new hardware or new use cases that existing systems do not support?


That sounds just like reducing a cost center to the point where new things become viable?




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

Search: