After 20 Years in IT Support, I Finally Started Building Instead of Just Fixing

Why frontend development finally clicked for me after years of troubleshooting software instead of creating it.

For most of my career, I’ve worked in IT support and technical troubleshooting roles.
I’ve spent years helping users solve problems, fixing systems, supporting enterprise software, and navigating the chaos that comes with technology in real-world environments.

Even before I worked in IT professionally, I was the kid taking apart watches, electronics, toys, and anything else I could get my hands on — then putting them back together without leftover screws or broken parts.

I didn’t just remove the obvious pieces either. I would completely dismantle things down to the frame just to understand how they worked.

But over time, I realized something.

I didn’t just want to support products anymore.

After years of troubleshooting enterprise software, I became increasingly aware of how many tools technically “worked” while still feeling frustrating and exhausting to use in practice.

I got tired of clunky interfaces, steep learning curves, and software that promised productivity while somehow making simple tasks feel more complicated.

That started changing the way I looked at technology entirely.

I didn’t just want to fix software problems anymore.

I wanted to build better experiences.

I became interested in the idea of creating tools that felt intuitive, user-focused, and visually engaging instead of overwhelming. For the first time, I started paying attention not only to functionality, but also to usability, layout, interaction, and design.

That eventually led me toward frontend development and UI/UX design.

Why Learning to Code Never Fully Stuck Before

I had tried learning programming before.

Like a lot of people, I bounced between:

• tutorials
• YouTube videos
• random online courses
• “learn to code” roadmaps

I would start strong, lose momentum, disappear for a while, then eventually come back and repeat the cycle again.

But no matter how many different things I explored, frontend development and UI/UX were what I always came back to.

Part of the problem was that a lot of coding education felt too abstract for the way my brain works.

I eventually realized that what I was missing wasn’t technology — it was creativity.

What finally made frontend development click for me was discovering the intersection between technical problem-solving and design.

Designing interactive layouts, improving user experiences, and seeing ideas come to life visually kept me engaged in a way backend-heavy learning paths never really did.

For the first time, it felt like I could combine my creative side with the technical intuition I’d built over years in IT.
And unlike some other areas of development, frontend gave me immediate visual feedback.

When I build something in frontend, I instantly see the result:

• layouts
• interactions
• responsive design
• UI changes
• real visual progress That made a huge difference for me.

Why Scrimba Felt Different

One thing that helped things finally click was finding interactive learning platforms instead of passively watching endless videos.
I started using Scrimba, and the experience felt much more hands-on and interactive than traditional tutorials.

It wasn’t just dry reading where words would start bouncing around on the page after every third or fourth paragraph.

I’m a very visual person, but I also learn best by actively doing things. Being able to pause lessons and directly edit the code inside the lesson itself made it easier for me to stay engaged and experiment while learning.

Instead of just watching someone code, I was actively building alongside the lesson.

It also removed a lot of the friction that used to frustrate me with traditional learning. I didn’t have to constantly bounce between a book, multiple browser tabs, and a separate coding environment just to follow along.
That kept me from drifting into what a lot of people call “tutorial mode.”

What I’m Actually Trying to Build

One thing I’ve learned is that I stay motivated much longer when I’m building projects tied to real ideas and real problems.

A lot of the concepts I’ve been exploring come from frustrations I’ve noticed over the years working with local businesses and technology.

For example, I started thinking about restaurant and food discovery platforms after realizing how difficult it can be for smaller local businesses to market themselves effectively online without spending huge amounts of money on advertising, analytics tools, or platforms with questionable ROI.

I saw a need for something more accessible — a way for local businesses to get visibility without needing massive budgets or complicated marketing systems.

That idea pushed me toward exploring concepts like:

• restaurant, brewery, and food truck discovery platforms
• local event discovery tools
• AI-assisted recommendation systems
• frontend experiences focused heavily on usability
• a retro and vintage clothing marketplace app

I’ve also started designing interactive layouts and UI concepts for some of these ideas, which has honestly been one of the most rewarding parts of learning frontend development so far.

Instead of endlessly collecting tutorials, I’ve been trying to learn through building.

That shift has probably helped me more than anything else.
Even simple projects feel more meaningful when they connect to something I genuinely want to create.

The Biggest Lessons I’ve Learned So Far

A few things have already become very clear to me.

Building teaches faster than consuming

Watching tutorials feels productive.
Actually building things exposes what you truly understand — and what you don’t.

Consistency matters more than intensity

I used to think I needed huge marathon study sessions to make real progress.
Now I’m realizing that smaller, focused daily progress is much more sustainable.

Frontend development fits the way my brain works

The visual feedback loop keeps me engaged in a way other technical learning paths sometimes didn’t.
Being able to immediately see layouts, interactions, and design changes makes the learning process feel much more tangible.

Learning in public is uncomfortable — but valuable

Writing this article is honestly part of that process.
I’m still early in the journey, but documenting the experience makes it feel more real and creates a level of accountability that I think is important.

What’s Next
Right now I’m focused on:

• improving my React skills
• learning Supabase
• building real portfolio projects
• exploring AI-powered product ideas
• becoming capable enough to ship actual applications

I still have a lot to learn.

But for the first time in a long time, it feels like I’m moving toward creating things instead of only supporting them.
And that’s been incredibly motivating.

If you’re someone trying to transition into development later in life or trying to find the intersection between creativity and technology, I’d genuinely love to hear about your experience too.

Thanks for reading.