My code wouldn't work last night.
What is annoying about this, is that I had convinced myself I was going to smash it.
To be completely honest, I had already mentally prepared a self-congratulatory tweet.
I knew entirely where I was going: I had thought through the tasks, thought through their order, had set up the files, organised my database, altered my layout, told Sinatra what complicated things I needed it to do.
I approached my laptop as an Eastern European gymnast approaches the horse. I was going to charge at that thing, execute precisely what I had prepared, and land smack bang on my dainty but training-hardened little feet.
And then came the Ruby. And the bugs.
Bugs used to freak me out. They were a sign of me not knowing anything - that what I had done was wrong, or how to correct it.
But very, very quickly with web development comes the realisation that bugs are your life. The bugs are the job.
(If I were training to be a chef, the bugs would be the burns. The reason chef's have asbestos hands.)
With writing, wisdom dictates your first draft will never be read so you should get it on the page as quickly as you can.
And coding is kinda similar.
From here on, I won't officially start a project until my first draft is complete and I will welcome in the bugs as a shepherd whistling for his flock.
The truly great thing about WDI - where there is no company clock ticking, or till ringing - is that I get the help I need to figure it out from people who have seen it all before have the patience to see it all again. And again.
On to the next one.