The document contrasts the roles of developers and programmers, emphasizing the importance of planning and design in software building to avoid disorganized coding. It advocates for Test Driven Development (TDD) as a crucial practice for enhancing code quality and preventing errors. Lastly, it encourages developers to continuously evaluate their coding practices and seek improvements.

1. Building Software vs
Programming

2. Who are you ???
a) The Developer
b) The Programmer
c) The nephew who makes websites
Developers are smart people, they think quickly and just try to reproduce
it with the same velocity.

3. Building Software
To build a software like a boss, first we need to:
- Think, discuss and design
- Use some good developer skills to start coding(will talk about later)
- Programmers skip those steps...

4. Headless chicken
Please, don't be a headless chicken that just runs without any thoughts

5. Why all that ?
- Time on planning/designing helps us understanding problems
- Time on planning == quality on delivery

6. Main Skill
Beyond these, a main skill to be improved is...
TDD

7. Test Driven Development
Provides us:
- Preventing future errors(not all but a lot) + saving time
- Helping on planning tasks
Please, spend some time on the mantra: red, green, refactor

8. What you have after that
- Beautiful and consistent code
- Beautiful and designed documentation
- Simple test, simple code. Easy to understand, easy to maintain
- Challenge to write better code == try to find better solutions == improve
your coding skills

9. You are smart, so ask
yourself:
- Is this test too trivial ?
- Is this test going to be useful ?
- Is this too complex ?
- should try another way, maybe trying to separate things first
- pair programming, if don’t ask google for samples
- if still complex, discuss about that again, probably this could be
easier to be done

10. Please tell me now:
- Do you use TDD or just write some tests ?
- Do you feel like a headless chicken sometimes ?
- What happen when you don’t plan or discuss about a new task ?
- What steps do you take when you get a complex task to be tested ?
- What could you improve to be a better developer ?

11. Bonus slide