Created
May 10, 2015 14:40
-
-
Save jakefolio/c898b387147578051f36 to your computer and use it in GitHub Desktop.
10 Steps to Maintainable Software
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Writing maintainable software is something we all strive to do when we start a project. | |
| The problem is, there is no simple checklist that states whether your code is maintainable or not. | |
| I once read it is much easier to recognize the absence of maintainable software than to define it. | |
| In this session we will lay out a foundation to building more maintainable software and practices | |
| to better your team workflow. We will cover anything from naming of methods/variables, VCS commit | |
| messages, and code reviews. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
+1 to everything above, from loving the title to needing more substance in the abstract itself. If you're not quite ready to write your 10 things list, then give us a clue - is it in automation? In frontend performance? In the frameworks we choose? In whether we use agile? Pick 3 or 4 things that you know will be themes and include them - then you can fill in the blanks in a panic when the talk gets picked :)