When you don’t know what you’re doing, I mean, quite honestly, you have no idea what you’re doing and you’re doing it for the first time – you have no idea what will happen when something goes wrong.

“I didn’t realize – EVERYTHING – was using that component I was working on and now everything is down” (Never happens).

But the more first times you go through, the more you think on your actions, the more you ponder the outcome and the more you worry, yes worry, about what happens when something goes wrong.  It can become paralyzing as you run through all the results and attempt to make it perfect.

“If this doesn’t work, I’ll be debugging for hours and hours, I better not run this until I have a free 2 – 3 hours afterward to look through it”.

This shouldn’t be the case though, you learn to be a bit more careful, but with everything else, who cares, break it (safely) and don’t do harm to your team and customers.

But don’t stop taking those first-time leaps, there is what got you where you are in the first place.

Want more? Check out my book Code Your Way Up – available as an eBook or Paperback on Amazon (CAN and US).  I’m also the co-host of the Remotely Prepared podcast.

Author

Write A Comment