If you can do either, you’re a developer ahead of the game of many others. These are two of the most important skills when becoming a developer because at their core they speak to creating and fixing code. Debugging – Walking through your own code to see if there are errors and/or running your own code to replicate errors. Troubleshooting – Getting an error sent to you that requires you to dig through the code…
I think it was Grade 10 or 11 and I was reading a book by Farley Mowat – perhaps Never Cry Wolf? To be honest, I can’t remember. But what I do remember is this one line that he wrote in it that went something like this (paraphrasing) – “When it’s cold outside, it’s the only time we can feel alive.” It’s cold outside. I can vouch for this and it’s a great feeling.
I had a horrible mic experience this past week recording and an episode of Remotely Prepared – turns out my mic defaulted to the wrong one and when I listened to the recording. It sounded like I was four tunnels below the surface, eating a sandwich. Not exactly the pristine quality we were hoping for. After realizing we would have to re-record, I then went through the arduous task of disabling mics I don’t use…
If you have ever written a line of code, you are a developer – it’s that simple. It doesn’t matter if you sold it. It doesn’t matter if you packaged it. It doesn’t matter if you promote it on twitter. It doesn’t matter if showed it. All that matters is that you wrote that line of code, you ran it, and it did something. If it shows “Hello World” on your screen, then congratulations you…
You only think you are. I wrote this a few weeks ago on the ItsYourTurnBlog. If everyone was moving ahead and there was no pandemic and you decided to take three months, six months, a year off, you wouldn’t feel like you were behind. Because it was your choice. This time it isn’t. Still no reason to feel like you’re behind.