Partners

This talk is geared towards open source contributors, but will also apply to anyone working in a tech firm, small or large.

The code that we write or bug reports we create will be read and reviewed by people from diverse backgrounds and skill levels. It is within the realms of possibility for our code to stand the test of time and especially in open source, for it to be read by thousands of open-source contributors many years into the future. It is our responsibility to write good, readable, legible code that abstracts away needless complexity and makes it a joy to be read and understood. Also, well-written code serves as a good example for future contributors and carries forward the culture of good code. The same goes for ticket descriptions that have well-written titles and summaries and bug-fix descriptions. In this talk, I will talk about how to write good readable code, ticket descriptions, bug patches et al in PHP and Javascript. I will quote many of the tips and best practices quoted in books like The Art of Readable Code, Clean Code by Robert C. Martin, Clean Code JS and Clean Code PHP and so on. This will cover things such as how to format code for readability, write good variables and functions, write well-contained functions and so on. The takeaway for developers would be on how to write beautiful code that improves the quality of code contributions to open source. After all, code is poetry.

Building for the underserved, solving for all
Building for the underserved, solving for all
Driving positive change through performance improvement plans
Driving positive change through performance improvement plans