What's in a Name?
It has often been said that there are only two hard problems in computer science: cache invalidation, naming things, and off-by-one errors. This presentation addresses the problem in the middle … For every minute you spend writing code in your career, you will spend at least 10 minutes reading somebody else’s code. Names matter. Spending time on naming things well is time well spent. Any developer, no matter what their skill and experience level, can become a better developer by learning how to be more effective at naming. Naming is more of a craft than a science, and yet there are a solid set of principles you can use to name things better. Come find out why we, as a profession, are generally bad at naming, how naming in software development has evolved over the years, and learn specific techniques to become a better namer.
John is a software architect and has been leading development teams for over 25 years. He's currently working for Improving in Houston as a principal consultant. He speaks frequently at conferences and user groups on topics as varied as agile practices, IoT, enterprise software, and functional programming. When he's not designing, writing, or talking software, you can usually find him reading and drinking craft beer.
- Houston Techfest 118 Recordings
- Developer 24 Recordings