2nd hardest thing in computer science
This talk is about naming things (modules, classes, methods, properties, variables) properly in order to improve code quality.
Have you heard about the two hardest things in computer science? It's cache invalidation and naming things. I want to focus on the second one.
Let's see common examples of both good and bad naming. What's the common part of each of them? What's makes names good? Can we settle on good enough or should we aim for perfect names? I'll show some of good and bad practices so you'll be able to recognize both of them when you make code review for your peers. Naming is one of two hardest things in CS, so I don't claim to be right about everything but I'm open to discussion and happy to learn from you as well.
Friday, 2017-10-06 @ 15:05
> Skill level: intermediate
> Duration: 25 min
Developer with 8 years of experience with backend systems. Created them from scratch by starting with analysis and writing specification up to deployment on production. Working mainly with Python, PHP and MySQL, elastic search and other technologies. Big fan and evangelist of continuous learning, organizer of many coding dojo sessions.