You’re writing code that works, and is covered by tests; if you’re not also clearly expressing the intent of your code, though, you’re only doing half your job. Programming languages are like any other language — a communication tool — and they can be learned as such.
Using the Four Rules of Simple Design as a starting point, this talk will cover the implications of those rules, why you should care about them and review your code against them, and how they naturally lead to more expressive code. We’ll look at examples and anti-examples of expression in English and code. At the end of the talk you will be able to use your programming language to clearly express a program’s purpose and stop writing the programming equivalent of legalese.
Who is it for?