So earlier this year I came across "The Art of Readable Code", an O'Reilly book about writing better, more maintainable code.
I found myself nodding in agreement at mostly everything in the book.
At about 200 pages, it's a quick read, so you should just go and read it. Honestly. Go.
You'll probably even be able to find a PDF somewhere.
Ok, well then.
What about if I gave a talk about a few of main points of the book? And used a lot of expletives for entertainment purposes?
Some topics we would cover:
- the importance of names
- when to comment your code
- making control flow understandable
- separating unrelated code
- code aesthetics
The book: http://shop.oreilly.com/product/9780596802301.do