Timeline for What can slow a developer down?
Current License: CC BY-SA 2.5
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 3, 2011 at 19:46 | comment | added | Homde | My experience says otherwise, but I guess it depends on the cowboy and the team :) I've learnt more by one week of coding and have done some code to show for it. Of course you'll have poor architecture if you don't do extreme and continuous refactoring and have a team/cowboy that's agile enough to keep up. Thinking you can do a "design phase", learn everything and do it right the first time is simply naive. The real value of a prototype are the lessons you learn, the you throw it away and do it right. Do that multiple times and fast :) | |
| May 3, 2011 at 15:06 | comment | added | Mike S | Experience says that it'll have poor architecture. Flying by the seat of your pants and cowboy coding are probably the worst things you can do during development. Having a design phase that will last a week, will save you months of programming and will lead to code that does what it's supposed to the first time around. The idea behind TDD is that you don't change the tests. Those tests are meant to emulate real-world usability, and if your code can't finish the test, then your code is wrong. | |
| Jan 6, 2011 at 6:55 | comment | added | Homde | Who says it'll be poorly architectured? I'm just saying that you don't want an excessive design phase and need to do lots of refactoring and re-architecturing during a project to arrive at quality code. On the other hand, for this to work you have to have clearly deliniated code responsibilities where different people aren't mucking around in each other's code. | |
| Jan 5, 2011 at 16:12 | comment | added | adamk | -1 I can understand your thinking, but the point of the design stage is to limit the need to refactor. It also facilitates unit testing which is great all the time for making sure something that was working doesn't get broken and released. If you don't do any planning, you will make everyone elses jobs harder when they have to try to maintain what will inevitably be poorly architectured code. | |
| S Jan 5, 2011 at 11:25 | history | answered | Homde | CC BY-SA 2.5 | |
| S Jan 5, 2011 at 11:25 | history | made wiki | Post Made Community Wiki |