One of the ironies of TDD is that it isn’t a testing technique (the Cunningham Koan). It’s an analysis technique, a design technique, really a technique for structuring all the activities of development. - Kent Beck’s “Test-driven development: by example”:
Next time you write a test, remember to answer all the questions:
- What are you testing?
- What should it do?
- What is the actual output?
- What is the expected output?
- How can the test be reproduced?
When you stop driving your design first, and primarily, through your tests, your eyes will open to much more interesting perspectives on the code. The answer to how can I make it better, is how can I make it clearer, not how can I test it faster or more isolated. - DHH
Should read in “Seven don’ts of testing” topic
nowadays, the most important quality of a developer is ability to learn new things quickly.
It is a pitfall to read everything.
9 women and 1 month do not a baby make
Junior engineers also don’t become senior engineers in a vacuum.
If a developer starts feeling too comfortable or too specialized, it’s time to rotate.
Knowing exactly what to code before coding transforms an intellectual and creative process into a mechanical process; in other words, it turns developers into code monkeys.
To summarize, this is wrong (because there is no “there”): Hey driver, how much will it cost to get there? And this is right: Hey driver, how much do you charge per mile, and do you have a map?
Vision: Industy/Socienty Connection: People Technical skill: computer
Entrepreneur: Invention & Vision Manager: People & Strategy Technician: Tools & Tactics