Good commit messages
Let others know what you did
Should be self explanatory
Should relate to code, not purpose or intent
We didn't teach you git for nothin !
Slide 4
Slide 4 text
Comments
Comment to explain on a per module basis
Travk complex changes in comments
Lost of authors
Licences
Automatic documentation
The squiggly things that begin with //
Slide 5
Slide 5 text
Loose coupling
Reduce inter dependency of code
Make generic classes
Abstraction
Code becomes easily testable and debuggable
This is just another buzz word filler....
Slide 6
Slide 6 text
Indentation
What?
It is important
Readability
Stick to the code guide.
Create one, if there isn't one
Choose from the big projects in the language you are coding in
Tabs vs Spaces
Missing semicolons
Slide 7
Slide 7 text
Variable names
There are two hard things in computer science: cache
invalidation, naming things, and off-by-one errors
Slide 8
Slide 8 text
Development Models
When will this lecture get over?
Slide 9
Slide 9 text
Waterfall Model
Slide 10
Slide 10 text
Iterative Model
Slide 11
Slide 11 text
No content
Slide 12
Slide 12 text
Some more buzz words
You don't need to remember them