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

None at all. Id recommend reading other people's code and thinking about it for a while.


Just out of curiosity: if you (or anyone else!) had to make a "must read code" list, what would be on it?


Gcc,gnome,openoffice - how not to do something.

FreeBSD,llvm,trac,vim - how to use sound engineering.


Anything written by Peter Norvig or D Richard Hipp.


Reading code is a great exercise and I've nursed a half-baked post on the topic for years now. However, I'm not sure that code reading is all that's needed.


What is considered good code to read?


If I knew the answer (of at least thought I did) then I could probably finish that post. ;-)




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

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

Search: