Code is Read
What separates the highly-skilled developer from the one fresh out of college? Why is it that some developer's code is far easier to maintain and others are nearly impossible to decipher? Both boil down fundamentally to whether you can easily understand the ideas and intent conveyed in their code. So what makes for easily understood code? There are some communication principles we can apply to our code to make it cheaper to change, and faster to understand. After all Code is read more often than it is written. It ought to be easy to read!
A surface level understanding of programming is necessary to gain the most benefit from this talk. A basic understanding of Modules, Variables, and potentially Classes are relied on in this talk. I believe anyone in the development space can benefit from this talk, results will vary based on exposure and experience.
- Enumerate principles which support more readable code.
- Learn to defend the link between Readable Code and more effective delivery
- Explain how common 'best practices' in development fit into and enable readable code.
Code is Read - Use Less Ram
Blog post on on of the key points in this talk. It introduces the concept of WetRAM, and how it should impact your development process. Then it explores some examples and potential improvements that can be made to improve Readability through optimizing use of this WetRAM.