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

> Existing code exerts a powerful influence. Its very presence argues that it is both correct and necessary.

I’ve probably paraphrased this line to every junior engineer I’ve mentored. It’s such a succinct and pithy insight.



It's what I call small 'c' culture, which regrettably, get's confused with 'C' culture. In software, 'C'ulture is:

- know your customer, and their use cases

- continuous improvement

- specialists have got to know the big picture and engage in it

- good cross functional coordination

- CS fundamentals: DBs, algorithms, UNIX, functional programming, C/C++, CDCI etc.

That never ages away.

However, stuff like we use and have always used Kafka (read the code!) for messaging, so we're not doing kernel-by-pass to move data now is small 'c' culture.

Small 'c' culture is the kind of stuff that, if you abrogate it, a small army of people will come out of the woodwork and brow beat you for it. Brow beating to keep you inline is not engineering. It's nagging.

Tradition, when it's small 'c', is stifling. Don't fall for it.




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

Search: