News for hackers. Stuff that matters.
Re:Ask HN: What is your best advice for a developer to write... by jacquesm on Wednesday June 29, 2016 @10:50AM (#12001975)
Read more good code and emulate after you fully understand it.

There are lots of projects that are good examples.

https://news.ycombinator.com/item?id=4331688

Re:Ask HN: What is your best advice for a developer to write... by collyw on Wednesday June 29, 2016 @11:30AM (#12002268)
The problem is that good code isn't so obvious that it is good, its just kind of there and understandable (as it should be). Bad code on the other hand is obvious that its bad, as it takes you ages to understand what is going on.
Re:Ask HN: What is your best advice for a developer to write... by Cyranix on Wednesday June 29, 2016 @03:28PM (#12004109)
Which is why I usually generalize this advice to "Read code". The majority of what you read should ideally be good code, but seeing both a good way and a bad way of doing the same thing is sometimes necessary.