3 technical milestones for an IT Pro's first 90 days back in tech after a long career gap

I'm a former IT professional with more than a decade-long career gap.

These milestones are a great start for someone like me with a long career gap in IT.

These milestones are what I'm striving for.

1. Refresh your coding fundamentals

Refresh your coding fundamentals by choosing one primary language, like Python.

If you are over 40 like me and returning to IT after a long career gap, it's tempting to jump straight into AI coding assistants, modern frameworks, and the latest development tools.

There is a better way.

Refresh the coding fundamentals you already learned years ago.

You don't need to start from scratch or spend weeks and months relearning everything. You need to rebuild the foundation you can use with today's tools.

Here are three reasons why:

Your coding fundamentals are still relevant, even if the tools have changed: Programming languages, frameworks, and development tools have evolved, but many core programming concepts remain the same. For example, variables, loops, conditionals, functions, and data structures are still essential. Problem-solving and logical thinking also transfer across programming languages.

You need to understand the code AI generates: AI coding tools can write code quickly, but you still need enough programming knowledge to determine whether it's correct, secure, and reliable. For example, AI-generated code might contain bugs, incorrect assumptions, and security vulnerabilities. If you understand programming fundamentals, you can spot when something doesn't make sense.

Refreshing fundamentals helps you rebuild confidence through small wins: After a decade away from programming, my biggest challenge isn't learning new technology. It's rebuilding confidence in my ability to write code.

And remember...

You aren't starting over. You're updating skills you already have.

You don't need to master every modern framework. You need a strong enough foundation to learn and adapt.

The goal isn't to become an expert in 30-90 days. It's to rebuild enough foundational knowledge to write simple programs, understand code, troubleshoot problems, and eventually build useful software with AI assistance.

Here are five practical steps to follow:

Choose one programming language to focus on

Refresh the core programming concepts you actually need

Practice coding every day with small exercises

Relearn how to debug and troubleshoot code

Combine your refreshed fundamentals into one small working program

Once you refresh your coding fundamentals, you're ready to build a real software project.

2. Build your first modern software project

It's time to put those refreshed skills to work.

Choose a project small enough in scope to finish.

It doesn't need to be complicated. The goal is to finish something useful, learn how modern development works, and prove to yourself that you can still build software.

Here are five practical steps for going from reviewing Python fundamentals to completing our first modern software project:

Choose one small project that solves a real problem: Build a website availability monitor that checks five websites, records their HTTP status codes and response times, and saves the results to a CSV file.

Break your project into small, manageable tasks: Before writing code, identify the individual tasks your program needs to perform. Experienced programmers may remember gathering requirements, writing pseudocode, or designing program logic before coding.

Learn and use a few modern development tools: Building a modern software project doesn't require mastering an entire new development ecosystem. A simple Python development setup might be Python, VS Code, Git, GitHub, a Python virtual environment, and an AI coding assistant. Start with Python, a code editor, Git, and GitHub.

Build the simplest working version and test it as you go: Focus on getting a minimum viable product (MVP) version working before making it more complicated. Get the MVP working, test normal and failure cases, and resist adding features that aren't essential.

Finish, document, and share your completed project: A completed, documented project provides more evidence of your skills than several unfinished programs. It doesn't have to be perfect. It means you've built something that works, and you understand how it operates.

You've refreshed your coding skills and built your first project.

Now it's time to choose one marketable technical skill to develop.

3. Develop one marketable technical skill

After being away from technology for a decade or more, deciding which technical skill to develop can feel overwhelming.

I feel overwhelmed.

More tools and technologies exist than ever before.

Here's the important distinction, though:

You don't need to learn every new technology. You only need to learn those worth developing.

Here are 5 reasons to consider when choosing which technical skill is worth developing:

Choose a skill that builds on your previous IT experience. Your previous technical experience is an advantage, even if the tools you once used have changed.

Choose a skill that solves real business problems. A technical skill becomes marketable when it helps an employer or client solve a meaningful problem.

Look for skills with evidence of current market demand. Look for evidence that employers and clients actually need it.

Choose a skill you can practice by building real projects. A technical skill is more useful when you can demonstrate it through completed work, not just claim you've learned it.

Choose a skill that can grow into other technical opportunities. Your first marketable skill should be a starting point, not a permanent limitation.

You don't need to catch up on every technology you've missed over the last decade.

You need to identify one valuable skill, build on what you already know, and learn to solve real problems with it.

Choose one skill to start with, like Python automation.

You can learn to automate file processing, analyze logs, and generate reports.

What should you realistically be able to do after 90 days back in IT?

Returning to IT after a decade or more can feel like starting from scratch.

Technology has changed. AI coding assistants are everywhere. Development tools and frameworks also differ from what you remember.

But 90 days isn't about catching up on everything you've missed. It's about rebuilding your skills, gaining confidence, and proving you can still solve technical problems.

By the end of those first 90 days, aim to have a working foundation, a completed project, and one technical skill you can keep developing.

Here are three realistic outcomes to work toward, and the ones I'm striving for too:

Write and understand basic code without relying entirely on tutorials or AI.

Complete one small, working software project.

Rebuild enough confidence to know what comes next.

I am in my first 90 days back in IT too, and I find it overwhelming to think about sometimes. I'm working on a 90-day plan, starting with the first 30 days of refreshing my coding skills.

Key takeaway: The goal of your first 90 days back in IT isn't to become the programmer you once were 10+ years ago. It's to become a capable, confident professional who can apply existing experience to today's technology.