Saturday, July 18, 2026

You Don't Need a Computer Science Degree to Land a High-Paying IT Job

You Don't Need a Computer Science Degree to Land a Great Technology Job

Picture of Home Lab

One of the biggest myths in technology is that you need a four-year computer science degree before anyone will hire you.

You don't.

In fact, many technology job postings include a phrase that most people completely overlook:

Bachelor's Degree OR equivalent experience.

That one word—OR—can change your entire career.

Most People Read It Wrong

When they see "Bachelor's Degree or equivalent experience," many people immediately eliminate themselves.

"I don't have a degree."

"I guess I don't qualify."

But that's not what the employer is saying.

They're saying there are two different ways to demonstrate your value.

The first is a college degree.

The second is proving you already know how to do the work.

Many hiring managers will gladly choose the second.

My Degree Isn't Even in Technology

My college degree isn't related to information technology.

I didn't earn a Computer Science degree.

I didn't major in Information Systems.

Yet even after retiring more than a year ago, recruiters still contact me several times every week—and sometimes several times a day.

My LinkedIn profile clearly states that I'm retired.

So why are companies still asking if I'm interested?

Because employers aren't calling about my diploma.

They're calling about decades of experience solving technical problems.

Experience Beats Theory

Over the years I've worked with technologies that businesses depend on every day.

Network engineering.

Enterprise networking.

Linux.

Network security.

Systems architecture.

Infrastructure design.

Automation and scripting.

Technical leadership.

Management.

These aren't just buzzwords on a résumé.

They're years of solving outages, troubleshooting complex problems, designing reliable systems, and helping organizations keep their businesses running.

Companies pay for results.

Experience demonstrates results.

Why Some People Hear Nothing but Crickets

I hear from people all the time who have submitted hundreds of job applications without receiving a single interview.

Many assume the economy is entirely to blame.

Sometimes it is.

But often there's another reason.

They're competing for jobs where thousands of applicants have nearly identical qualifications.

Meanwhile, there are other positions that employers struggle to fill because too few people possess the necessary skills.

That's the Law of Supply and Demand.

When your skills are common, employers have plenty of choices.

When your skills are rare and valuable, employers start searching for you.

How Do You Get "Equivalent Experience?"

This is where people become discouraged.

They think experience only comes from having a full-time job.

It doesn't.

You can build real-world experience by:

  • Building a home lab using inexpensive or retired computers.

  • Installing Linux and using it every day.

  • Learning networking with Cisco Packet Tracer, GNS3, or real Cisco equipment.

  • Learning PowerShell, Python, or Bash by automating repetitive tasks.

  • Building cloud environments using AWS, Azure, or Google Cloud free tiers.

  • Creating virtual machines and enterprise networks at home.

  • Volunteering to support technology for churches, nonprofits, schools, or small businesses.

  • Earning respected industry certifications.

  • Contributing to open-source projects.

  • Publishing your projects on GitHub so employers can see what you've built.

Every one of those demonstrates initiative.

Every one creates experience you can discuss during an interview.

Technology Rewards Curiosity

One of the things I've always loved about technology is that knowledge is available to anyone willing to learn.

You don't need permission.

You don't need a university classroom.

You need curiosity.

The internet contains more high-quality technical training today than existed during my entire career.

Thousands of hours of instruction are available for little or no cost.

The people who continue learning continue growing.

Don't Chase What's Comfortable

If your current skills aren't producing interviews, don't ask yourself:

"What job would I enjoy?"

Instead ask:

"What skills are employers struggling to find?"

Those are two very different questions.

The fastest way to improve your career isn't always finding a job you already know how to do.

Sometimes it's learning a skill that few other people have.

Your Career Is an Investment

A college degree is valuable.

For many professions, it's absolutely necessary.

But in technology, experience often carries just as much weight—and sometimes more.

Don't let the lack of a specific degree convince you that the door is closed.

It isn't.

Build skills.

Build projects.

Build experience.

The next time you see a job posting that says "Bachelor's Degree or Equivalent Experience," don't automatically disqualify yourself.

The employer may be looking for someone exactly like you.

Just make sure you can prove what you know. Are your skills in demand?

10 Technology Skills Employers Will Still Be Hiring For in 2030

No one can predict the future with certainty, but history has shown that businesses will continue investing in technologies that improve security, reduce costs, automate repetitive work, and increase productivity. If you're looking to build a career that remains valuable for years to come, these are the skills I'd be learning today:

  1. AI Automation – Using artificial intelligence to automate business processes and improve decision-making.
  2. Cybersecurity – Protecting organizations from increasingly sophisticated cyber threats.
  3. Cloud Computing – Designing, deploying, and managing services on platforms like AWS, Microsoft Azure, and Google Cloud.
  4. Linux Administration – The operating system that powers much of the world's servers, cloud infrastructure, and embedded devices.
  5. Scripting and Automation – Learning Python, PowerShell, or Bash to automate repetitive tasks and improve efficiency.
  6. Networking – Understanding how data moves across modern enterprise networks, including routing, switching, wireless, and software-defined networking.
  7. Virtualization – Building and managing virtual servers, desktops, and infrastructure that maximize hardware utilization.
  8. DevOps – Combining software development and IT operations to deliver applications faster, more reliably, and with fewer errors.
  9. Data Engineering – Collecting, organizing, and preparing massive amounts of data so businesses can make informed decisions.
  10. Infrastructure Automation – Using tools like Ansible, Terraform, and Infrastructure as Code (IaC) to deploy and manage technology environments at scale.

Notice something? Not one of these skills requires a specific college degree. They require curiosity, persistence, hands-on practice, and a commitment to continuous learning. The technology will continue to evolve, but one thing won't change: employers will always pay well for people who can solve difficult problems. Become one of those people, and you'll spend far less time searching for opportunities—and far more time deciding which ones to accept.

Why I've Been Retired for a Year and Recruiters Still Contact Me Every Week

 

I Retired Over a Year Ago... So Why Do Recruiters Still Contact Me Every Week?

"I've sent out hundreds of job applications and nobody is calling."

I've been hearing that a lot lately.

There's no question that today's job market is difficult in many industries. Good people are struggling to find work, and many have submitted hundreds of applications with little more than automated rejection emails—or complete silence.

So let me ask a question.



If the job market is so terrible, why do I still receive interview requests several times a week even though I retired more than a year ago?

My LinkedIn profile clearly says I'm retired.

Yet recruiters continue contacting me about desktop support positions, network engineering jobs, IT architecture roles, technical leadership, and management opportunities. Some weeks it's only one or two. Other weeks it's several.

The answer isn't that I'm special.

It's economics.

The Law of Supply and Demand

The same law that determines the price of gasoline, housing, and groceries also applies to your career.

When there are thousands of qualified people competing for the same position, employers can be extremely selective. Your résumé becomes one of hundreds sitting in a database.

But when there are more open positions than qualified people to fill them, recruiters start searching for candidates instead of waiting for applications.

That's exactly what's happening in some areas of technology.

Experienced network engineers, cybersecurity professionals, cloud architects, experienced systems administrators, AI specialists, and technical leaders are still difficult to find. Companies need those skills, and there simply aren't enough people with the experience they're looking for.

When supply is low and demand is high, opportunities follow.

Your Skills Have Value—But Only If Someone Needs Them

This is the difficult truth many people don't want to hear.

It doesn't matter how hard you work if your skills are no longer in demand.

It doesn't matter how loyal you were to your previous employer.

It doesn't matter how many years you've been doing the same job.

The market decides what skills are valuable today—not what was valuable ten years ago.

Technology changes.

Industries change.

Businesses change.

The people who adapt usually have more opportunities than those who don't.

Stop Asking, "What Do I Want to Do?"

Instead, ask:

"What skills are employers desperately trying to find?"

Those aren't always the same question.

Most people begin by looking for jobs they think they would enjoy.

There isn't anything wrong with that.

But if you've been sending out hundreds of applications without results, it may be time to change the question.

What industries are growing?

What certifications are employers asking for?

What technical skills appear over and over in job postings?

Where are companies willing to pay premium salaries because qualified people are hard to find?

That's where opportunity usually lives.

Reinvention Isn't Easy

I've reinvented myself more than once.

I started as an Air Force medic. Later I taught myself hospital computer systems. Eventually I moved into network engineering, architecture, and leadership.

None of those transitions happened because they were easy.

They happened because I recognized where demand was growing and invested the time to learn new skills.

Every new skill increased my value in the marketplace.

Invest in Demand

If you've sent out hundreds of applications and all you hear are crickets, don't assume you're the problem.

Instead, honestly evaluate whether your skills match today's market.

You cannot control the economy.

You cannot control hiring managers.

You cannot control how many people apply for the same position.

But you can control what you learn next.

The job market rewards people who solve problems that employers desperately need solved.

Find out what those problems are.

Learn the skills to solve them. Read my posts about job skills and free education.

When your abilities are in short supply and high demand, employers often start looking for you instead of the other way around. Do you really need that expensive degree?

Saturday, July 4, 2026

The School Bus Ride That Taught Me I Was Poor

 

The Day I Realized I Was Poor

Most poor folks don’t know they’re poor.


That may sound strange to someone who never lived it, but it’s true. When you grow up in poverty, you don’t wake up every morning thinking, I’m poor. You just wake up. You put on whatever clothes are there. You eat whatever food is in the house. You live in whatever house your family can afford, even if the floor is weak, the walls are thin, and the winter air comes through every crack.

You don’t know it is poverty.

You think it is normal.

At least I did.

When I was a boy in Alabama, I didn’t understand that other people lived different from us. I knew some kids had nicer things, but I didn’t have the words for it. I didn’t understand class. I didn’t understand generational poverty. I didn’t understand that some children went home to warm houses, full refrigerators, clean clothes, and parents who had a little money left after payday.

All I knew was the life in front of me.

Hand-me-down clothes were normal. Ragged shoes were normal. Bologna sandwiches wrapped up and carried to school in a brown paper sack were normal. Houses that looked tired before you even walked inside were normal. People speaking with a heavy Alabama accent was normal. Working hard and still not having enough was normal.

Then one day, riding the school bus, something changed.

A classmate started making jokes about my clothes.

They were raggedy hand-me-downs, the kind of clothes that had already lived a hard life before they ever got to me. To me, they were just my clothes. They were what I had. But to him, they were something to laugh at.

Then he asked me how long it took me to learn how to make candles from a turtle shell.

Everybody who heard it knew what he meant. It was not just a joke. It was meant to put me in my place. It was meant to say, You are different. You are beneath us. You are poor.

I don’t remember what I said back, if I said anything at all. Sometimes when a thing cuts deep enough, words don’t come right away. You just sit there and take it. You look out the bus window and act like it didn’t bother you.

But it did.

That night, I thought about what he said.

I thought about my clothes. I thought about his clothes. I thought about how he looked when he got on the bus compared to how I looked. I thought about the house where the school bus stopped to let him off. I had seen it before, but I had never really looked at it.

Now I did.

His house looked solid. It looked finished. It looked like somebody had money enough to keep it that way. It did not look like the cheap houses I knew. It did not look like a place where life was always one broken-down car, one unpaid bill, or one bad week away from falling apart.

That was the first time I really started comparing.

Not because I wanted to feel sorry for myself.

Not because I wanted to hate him.

But because his words forced me to see what I had not seen before.

The next few days at school, I watched him more closely. He wore nice clothes. Not fancy clothes, but clean, decent, fitted clothes that looked like they had been bought for him. He did not come to school in worn-out hand-me-downs. He did not pull a bologna sandwich out of a brown paper sack like I did.

Then I started looking at the other kids.

Some were dressed like me. Some looked like they came from the same kind of struggle I came from. But most were not. Most had better clothes. Better shoes. Better lunches. Better haircuts. They seemed more comfortable in the world.

Then I started listening to how they talked.

Some of them sounded more articulate. More educated. More confident. They spoke like they expected to be heard. They did not sound like they were already apologizing for where they came from. They did not get laughed at for their Alabama accent, at least not the way poor kids did.

That was another hard lesson.

Poverty is not just about money.

Poverty shows up in your clothes. It shows up in your lunch. It shows up in your teeth, your shoes, your haircut, your house, your words, and sometimes even in the way you carry yourself.

It shows up before you ever say a word.

And the painful truth is this: other people often see your poverty before you do.

I had been poor my whole life, but I did not know I was poor until someone else pointed it out in a cruel way. That school bus ride did not create the poverty. It only opened my eyes to it.

That realization hurt.

It hurt because I could not unsee it.

After that day, I noticed everything. I noticed when other kids had things I did not have. I noticed when my clothes were different. I noticed when my lunch was different. I noticed when someone talked down to me. I noticed when people assumed I was less intelligent because of how I dressed or how I spoke.

And I noticed something else too.

I noticed that poverty has chains.

Some of those chains are obvious. No money. No reliable transportation. Bad housing. Limited opportunities. Poor schools. Parents struggling just to survive.

But some of the chains are invisible.

You can start to believe that poor is all you are. You can start to believe that people like you are not supposed to speak well, dress well, learn more, earn more, or live anywhere better than where you started. You can start to accept poverty as your assigned place in life.

That is one of the most dangerous parts of poverty.

It teaches you to call survival normal.

It teaches you not to expect much.

It teaches you to stay in your lane, even when that lane is nothing but dirt, dust, and dead ends.

But you cannot escape something until you first realize you are trapped in it.

That school bus insult hurt me, but it also woke me up. I did not know it at the time, but that moment planted a seed. It made me start asking questions.

Why do they have more than we have?

Why do they speak differently?

Why do they seem to know things I do not know?

Why do some people expect a better future while others just hope to get through the week?

Those questions mattered.

Because the day you realize you are poor is not just the day you feel shame. It can also become the day you begin to fight back.

Not with anger.

Not with excuses.

Not by pretending poverty is someone else’s fault every time.

But by looking at your life honestly and saying, This is where I am, but this is not where I have to stay.

That does not mean escaping poverty is easy. It is not. Anybody who says poor people can just “work harder” has probably never been poor. Poor people already work hard. They work tired. They work sick. They work with bad shoes, old cars, empty refrigerators, and bills stacked on the table.

Working hard matters, but working hard by itself is not always enough.

You also have to realize where you are. You have to learn what you were never taught. You have to watch people who are doing better and ask what they know that you do not. You have to improve how you speak, how you think, how you handle money, how you make decisions, and how you see your own future.

That is not selling out.

That is survival with a plan.

I did not realize all of this as a child on that school bus. Back then, I only knew that I had been embarrassed. I only knew that a boy had made fun of my clothes and used one cruel sentence to make me feel smaller than I already felt.

But looking back now, I understand something.

That was the day I realized I was poor.

And as painful as that lesson was, it was also one of the first steps toward escaping the chains of poverty.

Because poverty can keep you blind if you let it.

It can convince you that hunger is normal, ragged clothes are normal, bad housing is normal, being laughed at is normal, and expecting less from life is normal.

But the moment you see it for what it is, something changes.

You may still be poor.

You may still be wearing the same clothes.

You may still be carrying that same brown paper sack lunch.

You may still live in the same cheap house.

But now you know.

And knowing is the beginning.

Realization can be a painful lesson, but sometimes pain is what wakes us up. Before you can break the chains of poverty, you first have to see them.

I saw mine on a school bus in Alabama.

And I never forgot it.

https://www.steviegdavis.com/2026/10/cheap-houses-paying-it-forward-to-help.html

TD Bank's $250 Minimum Balance: The Cost of Being Poor

  TD Bank's $250 Minimum Balance: The Cost of Being Poor Why do banks keep finding ways to take money from the people who can least aff...