“Pseudocode is a step-by-step description of an algorithm written in simple English using a code-like structure.
It is designed for human understanding, not for machine execution, and does not follow the syntax of any programming language.” (Good old GeeksForGeeks.com)
What might it have looked like if I had pseudocoded my career change journey before it ever started, 15 months ago?
#I should define my goal: a new career as a data engineer that uses my skills in problem solving, pattern recognition, project management, handling large datasets (I used to call these books), and considering how we use technology in the bigger context of *gestures at everything*
#Make sure my old office on campus is clear. Lament the final journey out of the car park and the fact that I don’t have enough shelf space at home.
#Import necessary new libraries. Yay. I love libraries in every context.
#Language can be slippery between disciplines and phases of life, so pick up learning Python. Enjoy how logical and clear this programming language is and ignore my programmer friend when they scoff “oh, Python is my least favourite.”
#Make a ‘hello world!’ file. Make a password generator.
#Replace my laptop’s Windows operating system with Linux. Hit a problem and realise I need to use the terminal. Look up bash commands on phone. Solve problem. Feel like absolute Queen of All the Computers in the Universe. I can do anything I want!
#Map out the logic of my next steps. Bootcamp, find job.
#This is much more complicated, but that’s ok! Knowing the overall logic well is great for motivation. Fill in the details one day at a time…
#And so I have 🙂