The Real World Transition…
From the Lecture Halls to the Workplace.
Picture this: you’re fresh out of university, armed with all the knowledge from meticulously structured Udemy courses, YouTube tutorials, and perhaps a touch of nostalgia for those now-familiar lecture halls and computer labs. You feel ready to dive head-first into the world of cloud consultancy. But wait, what’s this? 9 am, day 1: You can’t follow anything! The code isn’t as pristine as those textbook examples, and there’s no professor to offer a reassuring nod when you’re in doubt. You’re wide-eyed, like a brand-new pilot suddenly having to grab the controls. Yes, it’s a tad terrifying! Welcome to the real world!
Having just graduated with an MSc in software development and having been working at Version 1 as a DevOps Engineer for a while, here are some pointers around the differences between study and practice.
1. The Good, The Bad, and The Ugly (Code)
Recall the crisp and clean code you tackled during your studies? Well, brace yourself, because real-world code can be messier than a teenager’s bedroom after a weekend binge of video games and junk food. It isn’t always neatly documented, is sometimes tangled, and often feels like you’re deciphering ancient hieroglyphics.
Code is created as a solution, not a teaching tool. Over time, as multiple developers contribute, it morphs, often drifting far from its pristine origin. Despite everyone’s desire for perfection, the reality of deadlines, evolving technologies, client feedback, technical debt, and new features make this challenging. If this can happen with a university assignment, imagine the scale of change in large software projects. After all, pursuing perfection can sometimes sideline progress.
Takeaway: If you find yourself thinking, “Who wrote this spaghetti code?!” — more often than not, it’s someone just like you and me. Someone doing their best. Instead of pulling your hair out, embrace the challenge. Messy code is simply an opportunity in disguise. This leads me to…
2. Reading is to the Mind as Following Pre-Written Code is to the Developer
One of the most underrated skills in tech? Deciphering and building upon someone else’s code. Imagine diving into a detective novel, but instead of uncovering the culprit, you’re decoding the method. Mastering this is not just about understanding but about adapting and extending. This challenge can intimidate newbies, but like any skill, exposure and practice will enhance proficiency.
Takeaway: Before attempting to rewrite the entire codebase, take a pause. Get into the Sherlock Holmes mode and dissect the existing code. In most cases, there’s method to the madness (and where there isn’t there’s ‘Technical Debt’!).
3. The Sacred Art of Source Control
Academia rightly emphasizes coding prowess but often skims over a pivotal aspect: effective source control. In the professional sphere, being able to effectively use GitHub, GitLab or your other chosen source control tool is akin to harnessing the Force in Star Wars. Mishandle it, and chaos ensues — lost versions, overwritten work, and more. While some leeway is given for beginner errors, many courses undersell this crucial facet of the job.
Bonus: Master the craft of meaningful commit messages. During bouts of frustration, it’s easy to neglect this, but clarity here is paramount. A touch of humour is acceptable, provided it remains professional. A personal favourite of mine? “Make the string you made a string a string” — it’s as accurate as it is whimsical!
Takeaway: Dedicate time to source control nuances. It’s a shield against countless potential blunders.
4. To Ask or Not To Ask? Always Ask!
In the professional realm, silence isn’t golden; it’s risky. If you’re lost, it’s better to be the person who asks questions than the one who nods along, only to end up causing a digital catastrophe later on. Every professional was once a beginner, and they understand the value of clarity.
“Where knowledge ends, guessing begins.”
Takeaway: If you’re in doubt, shout (well, not literally). No one ever got an award for keeping quiet and hoping for the best.
5. Agile is real and it’s everywhere!
In the constantly evolving landscape of IT, the Agile methodology has transcended from being a mere buzzword to a concrete practice that teams around the world swear by. Unlike traditional models, Agile embraces change, fostering an environment where teams can swiftly adapt, making projects more resilient and outcomes more aligned with ever-shifting client needs. At the heart of this approach are a few essential ceremonies and terminologies. While some newcomers to the industry might shrug them off as mere jargon, understanding these concepts can be a game-changer.
Takeaway: Engage proactively in stand-ups, delve into sprints, explore backlogs, participate in refinements, and attend show and tells. Being Agile-informed is empowering. Why linger on in silence?
6. Time keeps on ticking!
Transitioning into the professional world often comes with a whirlwind realization: the pace is unyielding. Gone are the days of prolonged deadlines and extended grace periods typical of academic settings. In the industry, timelines are compact, stakes are high, and every minute counts. Tasks, projects, and meetings seem to whirl by in a constant stream, and there’s an underlying rhythm that demands quick thinking, swift decision-making, and efficient execution. The cadence of this environment can initially feel overwhelming, but it’s also invigorating, pushing professionals to optimize their work habits, prioritize effectively, and evolve continuously.
Takeaway: Embrace this swift rhythm. Leverage tools to bolster productivity and recall: the brisk pace, though challenging, fuels growth and innovation.
7. The Graduate to Engineer Evolution
Lastly, always remember, that every seasoned professional once stood where you stand today. The transition might feel like climbing Everest, but with determination, grit, and a dash of humour, you’ll soon find yourself at the summit, waving the flag of an accomplished engineer. You will make mistakes, but you will learn more from those mistakes than you will from any lecture, online course or book.
Takeaway: Personal evolution is a marathon, not a sprint. Relish each lesson, draw wisdom from every hurdle, and have unwavering faith in your career path.
8. The Company you keep
I joined Version 1 after being aware of them as a company even before I decided to re-enter the industry. I had seen the “Best Place To Work” awards and the intriguing core values including “No Ego”. I thought “If I ever go back to working in IT, I want to work for a company like Version 1.” I never quite expected it to happen the way it did, but I have been blown away by the generosity of my colleagues in terms of time, knowledge and encouragement. The core values are, literally, core values and you will find that they resonate deeply with everyone at Version 1. If I hadn’t found such a supportive home, I’m not sure I could have lasted these last few years. Make no mistake, the move from the lecture halls to the workplace can be tough.
If the company has a graduate programme, that might make the acclimatisation process much easier. Version 1, for example, has the “Assured Skills Academies” which prepare candidates for the ‘Associate’ role within Version 1. This 8-week academy and 18-month associateship help prepare and guide newcomers into the industry in a safe and supportive way. Yes, it is a job, and yes there will be pressures, but having this programme means that the pressure won’t turn into stress.
Takeaway: Try to choose the company you work for as much as they will choose you. An interview should be like a first date, it only leads to happiness if there is a mutual attraction and respect. Do your due diligence and make sure you know about the companies and roles you are applying for.
In conclusion, the move from university to the professional world is often less about the technical skills you’ve learned and more about the attitude you adopt. Embrace change, be curious, ask questions, and remember, it’s okay to find moments of joy and laughter along the way. Welcome to the world of Cloud Consultancy!
This blog was written by myself, and proofread by ChatGPT.
About the author
Thomas Watson is an Azure DevOps Engineer here at Version 1.
