Timeline for How to become a "faster" programmer?
Current License: CC BY-SA 2.5
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 27, 2010 at 18:32 | history | migrated | from stackoverflow.com (revisions) | ||
| Jun 2, 2010 at 20:55 | comment | added | Donal Fellows | Tests are good because they help you keep problems fixed. | |
| Sep 12, 2009 at 19:07 | comment | added | bryanbcook | @Konstantin, if you consider "development" to be the act of writing the code statement, I would agree with you. However, if you consider "development" to include packaging, preparing build notes, deploying, testing, producing defect reports, reviewing and prioritizing defects, task assignment, investigation, debugging and fixing and starting the process over again -- then the 15 minutes to write the unit test outweighs the days and loss of customer confidence 1000x over. | |
| Sep 12, 2009 at 18:54 | comment | added | Esko Luontola | If the management does not understand some key concept, you should explain it to them. For example martinfowler.com/bliki/TechnicalDebt.html | |
| Sep 12, 2009 at 18:53 | comment | added | Esko Luontola | Typing has never been the slow part of programming. Even though you need to type more with TDD, it does not slow you down. It might even speed you up, because writing a test first helps you to focus on what is needed before thinking about how to implement it. | |
| Sep 12, 2009 at 18:51 | comment | added | Esko Luontola | @Konstantin: Writing some code using TDD might take take 20% longer, but it also yields better code and in the long run, when the system grows, the speed of making changes stays about the same. TDD helps you to avoid technical debt which slows you down. | |
| Sep 12, 2009 at 8:33 | comment | added | Konstantin Spirin | TDD is much slower than dirty coding when you need to make a quick fix. Often you have to write 5 lines of code to test 1 line fix. Bad thing is management usually needs fast solution and rare understands concept of coding and architectural debts. | |
| Sep 11, 2009 at 16:22 | comment | added | Frank Schwieterman | When doing TDD, you have a test runner that produces a red/green report per test to indicate if they pass. | |
| Sep 11, 2009 at 15:14 | comment | added | JB King | I believe this is either using a tool like Resharper that can verify coding standards or running automated tests that if any fail, that's red and if none fail then it is a "green" result similar to how cars go on a green light and stop on a red light. | |
| Sep 11, 2009 at 15:06 | comment | added | Graeme Perrow | Can you define "Go green" for those of us who have no idea what you're talking about? :-) | |
| Sep 11, 2009 at 15:00 | history | answered | bryanbcook | CC BY-SA 2.5 |