how to (did I learn to) build (high) quality software product
what quality means to you, employer and customer
me
- coding since 2000- crap until 2010- my shitty experience
methodology
- agile- waterfall- whatever..
source control
- branching- integration – deployment- quick and offline- always releasable
team collaboration
- solo developer?- tools, such as hipchat, skype- email…? grow up.
education
- self-learn- learn on the job- try new- follow someone
- twitter- flipboard
tools
- code quality tools like resharper- ide- faster and fun
tests
- automated most- a lot of it- manual - yes- unit testing- test frame work
CI
- solve problems quickly- cheap- visibility- confidence- no waiting- Jenkins, Hudson, bamboo
coding
- function – can you see?- unit testing- tdd, bdd- code climate- best practice
- align- comments- dry- inventing wheels
technical debt
- don’t leave behind- don’t make others to fix- you are broken in no time- broken windows
pair programming
- involve- teach- learn- help
feedback
- don’t be shy- say it as it is- give & take- vegas – stays there- client feedback