10
A hackathon in Austin taught me to always test my code early
I was at a local hackathon last month, trying to build a simple weather app. I spent the first 4 hours just writing code without running it once. When I finally hit 'run', my screen filled with over 50 error messages. I had to spend the next hour fixing basic syntax mistakes I could have caught in 5 minutes if I tested as I went. Now I run my code after writing every small piece. Has anyone else learned this the hard way?
2 comments
Log in to join the discussion
Log In2 Comments
the_mason3d ago
50 error messages" is the classic programmer wake up call.
2
wyatt_green3d ago
That "wake up call" thing is so real. It's like when you try to fix one small thing in your house and suddenly you're looking at five bigger problems you never knew about. The first error is just the tip of the iceberg.
2