From Iron Worker to Code Writer: How I Transitioned from Building Structures to Building Software

A few years ago, I made one of the toughest decisions of my life: to completely change the direction of my career. I transitioned from hands-on work in construction to the world of IT development, and I did so at an age where I didn’t consider myself young. Most of my more experienced colleagues were a generation younger and had studied the field at university.

What challenges did I face at the start? What might I have done differently in hindsight? What were my biggest fears? Was it ultimately the right decision? I hope my story inspires—and perhaps reassures—others who are considering taking a similar leap.

Why Make Life Difficult for Yourself?

I used to travel abroad a lot for work. Sounds great, right?

Most people see travel as a valuable asset to any career, but when my wife and I decided to have a baby, we logically realized that watching him grow up through a webcam wouldn’t be ideal. Despite my extensive experience in building warehouse systems and some notable management successes, there wasn’t much demand for my skills locally. While I had job offers from abroad, my family and I were determined to stay in the Czech Republic. It seemed like the right time to try my luck in a different field.

After some consideration, I landed on programming. For some, the promise of better earnings is the main draw, but I was primarily driven by one particular personal interest—Apple. I’d always been a huge fan of the brand, watching every keynote religiously, and that passion led me to start experimenting with Swift, the then-relatively-new programming language.

„For some people in IT, the prospect of a better income is appealing, but for me, it was primarily about my passion for Apple.“

I admired how Apple actively promoted programming education in this language, particularly through tools like the Playgrounds app, where kids learn programming logic by guiding a character through a maze using a set of commands, or through resources like Intro to App Development with Swift. Apple’s promise that “anyone can learn to code” was incredibly motivating for me.

But really—anyone? Could I? Back in high school, I hated programming. Our teacher’s attitude didn’t help; she seemed determined to prove how complicated programming was, as if it were reserved for a chosen few.

A Self-Experimenter’s Journey

I was learning through publicly available resources and publications, but I still felt like I was missing a comprehensive perspective. I had pieces of the puzzle, but I didn’t know how to fit them together. Looking back, the best decision I made was to create my own project, and if I could do it again, I’d start much sooner.

My app is called chytrak.eu. It’s not super complicated, but that was intentional. It wasn’t about creating something overly ambitious or unattainable; quite the opposite. I wanted to build something with a realistic chance of being completed. The goal was to create a practical playground where I could apply what I was learning in theory while also encountering real-world problems that would teach me to reach solutions independently.

"In hindsight, I would have started my own project much earlier—long before I felt I knew even a little.”

While creating my own app, I went through the entire development process and gained a deeper understanding of the tools and concepts that weren’t often covered in online courses. For example, I learned about using design patterns, version control, the principles of writing clean and sustainable code, and the importance of adhering to a consistent architecture. Most importantly, I didn’t just learn that these things exist—I gained practical insight into why they matter.

My app, chytrak.eu, currently has tens of thousands of downloads and even provides a nice supplement to my salary. Not to mention that having your own project is a significant advantage when looking for a job.

Professional Growth

The little experience I gained from creating my own app helped me land a trainee position at MeguMethod. Even though I lacked some basic skills, like working with a terminal, I got the opportunity thanks to the foundation I built at a half-day bootcamp.

I’ll admit, the beginning was tough. My colleagues were extremely busy, and there was a lot of pressure on me to become independent as quickly as possible. I doubted myself often, but I realized I needed to stop focusing on what I couldn’t do and quit comparing myself to others. Instead, I started setting small, manageable goals—focusing not on what tomorrow might bring, but on what I needed to accomplish right now.

"I often doubted myself, but I knew I had to stop focusing on what I couldn’t do.”

Additionally, I had no safety net to fall back on, as I had severed all ties with my previous career. The only option was to move forward. Having just one path with no alternatives became a powerful motivator to keep pushing ahead.

What Would I Have Done Differently?

Looking back, here's a list of things I wish I'd been able to tell myself:

• Stick to iOS development: I wouldn’t change the field I chose because it genuinely interests me.
• Start your own project earlier: I’d begin creating my own project right from the start of studying theory.
• Publish your project: I’d aim to share my project publicly rather than keeping it tucked away in a drawer.
• Network actively: From the beginning, I’d seek out more IT contacts, ask them about company processes, tools they use, and team dynamics. Joining professional groups, finding a mentor, and attending meetups to build skills and connections would be a priority.
• Focus on practice, not rote learning: Practice is what teaches the important things and makes them stick.
• Be patient with understanding: I’d accept that I won’t understand everything right away. Sometimes it’s more effective to step back and let things click later in a different context.
• Ask more questions in a new job: I’d be more proactive in learning about company processes from the start—like how budgets are managed, when to seek help if I’m stuck, and where my hourly reporting fits into the bigger picture.
• Embrace agency work again: While it can be high-pressure at times, the experience gained from working on different types of projects is invaluable, and when the team is as great as it is here, they balance out the challenges beautifully.

In retrospect, and despite the challenges, I believe that my transition was absolutely worth it. Working behind a computer has given me greater freedom—I can theoretically work from anywhere and plan my hours to suit my needs; at least, that’s how it works here at MeguMethod. This flexibility allows me to spend more time with my family, which is incredibly important to me.

Additionally, I’m constantly challenging my brain, which I value deeply. There’s nothing worse than letting your mind stagnate—and that’s something that never happens in a development job.