Hacker News Reader

Comment by bobobjorn | Hacker News Reader

But if people then want your code, your stuck with code without tests. That you at most, can retro fit tests to.

except the code already works right (in proportional to your skill). and if it stops working right you did something bad. and you're using version control, so you can do diffs, rollback, do branches/forks, experiments, etc. This is a much faster workflow than being weighed down by automated test baggage. Again, some folks hold the code in their mind and do a very good job of making perfect incremental changes, only moving forward, no regressions. (not 100% of the time, but with experience/skill you can approach that, especially before you end your dev session for the day.)

If thoose folks exists, i have never met any. And if they exist, they are few. And if i then need to hire more people to work on the project. Im pretty much out of luck. Even if i know i write perfect code (i dont). I wouldnt trust everyone that will work on my code to write perfect code.

relax uncle bobo ;) I'm a general proponent of testing, but this is a game and as such the feeling is more important, not everything is capturable by tests.

Notch is creating right now, watch http://vimeo.com/36579366 "inventing on principle" which explains the importance of immediate visual feedback.

Also give him just a "little" credit for minecraft

Yes, i dont mind that notch is writing code without tests.

I just dont want anyone else to think it is a good idea for them :-)

"At most"?

The tests can be the same or even better that those added at some TDD style.

And, in either case, that would be a nice problem to have.

Depends on how long ago you wrote the tests. Pretty soon the tests you will write, will most likely test that the code does what it does. Not what it should do.

And yes, it is a better problem to have, then to have code that noone wants.

Reply on news.ycombinator.com