|
|
|
|
|
by cringepirate
2120 days ago
|
|
I personally I make sure I have some form of automated testing (normally unit tests and e2e tests). As I like to know my code works but I can't do the writing tests first. It just doesn't work with how I approach problems. The approach I have to many projects is: 1) Sketch out a rough idea of how I will build it.
2) Try to get the fundamentals working,
3) Start building and fixing any obvious defects in the design. Add tests as I go along to catch obvious defects.
4) Iterate from there to completion. For most of the projects I am working on this seems to be fine. |
|