On Error Resume Next
This story will try to dig deeper into my personality through assessment of skills I had, I lost or think I have lost.
As far as I can remember I have always wanted to be a computer games engineer. As a kid I played with qBasic, Pascal, Logo and then later tried to develop alongside my childhood friend and great engineer Tomislav. We have crafted many applications for Windows and Web.
Back then it was fun to create SMS push and pull apps, Remote Desktops before Windows had them and online search engines. It has soon displayed as a very hard thing to do. My short temper and lack of precision did not help for sure.
Recently I have become very conscious about the fact that I was a lousy engineer. Today I am running a high tech startup with the emphasis on high. We are running sensors here, a full stack of web technologies, computer vision tech backed by proprietary iPad apps etc. Somehow we manage to navigate through the jungle. These days I really miss my engineering roots so I have decided to revisit them just for the sake of feeling better in communicating with my team and to know how to set expectations.
Having said that I have designed, debugged and ran my first iPhone app. Xcode, happy to meet you.
I had an instant feeling of satisfaction as I felt this is how we continue the legacy which was born around 1998. During my session with the old times an instant burst of memories came through the abyss.
It was a command from Visual Basic I have used in all of the code I crafted.
ON ERROR RESUME NEXT.
In fact I have seen that this particular command is built into my personality. Sometimes when a run-time error of my life occurs I just proceed to the next command. Or as my friend Marko would said: ON ERROR ACCEPT LEARN AND RESUME NEXT.
It is paramount that we embrace our errors and expect we will do many others but not the same ones.
Tnx to Maja, Marko for feedback