If I could travel back in time and give the rookie developer version of myself an hour of advice, this session will be that advice. I'm specifically focusing on advice that will help us write better code. I've written a lot of horrible code in my career, and learned a lot of lessons in the process. In my day job I also get the opportunity to look at a lot of other teams code, and help them clean it up. Over my career I've gotten a pretty good idea of what I believe are the most important lessons when learning to write "good" code. And here's a hint, it's not neatly captured in the SOLID set of principles that seem to be so popular at conferences these days. Expect a lot of examples and concrete advice that you can take away and start applying immediately to improve your code.