When Will The Tech Jobs Come Back?

share job tips
1 follower
2 Video Views·Oct 7, 2024
When with the software developer jobs come back? A few different ways to consider how things might pan out, ranging from traditional interest rate models to the impact of low-code/no-code, AI and robotics on investment.
Hi, my name is Will, and I've been working in software development for several decades
now.
I started in the 90s in Silicon Valley working for companies like Apple and Symantec, and
then I moved into consulting in the 2000s.
I've written four books on software development, and I built and sold an 85-person software
development consulting company, which gave me a chance to work with a lot of companies,
everything from startups to a lot of the big Fortune 500.
So today, I wanted to talk a little bit about a topic that's on the mind of a lot of folks,
and the question is, when will the tech jobs come back?
I did another video about some of the layoffs and talking with a recruiter, you can go check
those out, but at some point you start saying, okay, well, we know that the layoffs are happening,
when will the jobs come back?
The most obvious simple answer is when interest rates drop and money is cheap, right?
The jobs come back.
If that's the answer, then you can bookmark this webpage, the FRED website, and take a
guess.
Looking at that chart, I'm going to guess it could be anywhere from this summer to two
years from now.
The outside barrier on that, I would guess, would be if college enrollments in computer
science drop off a lot now, then it could be closer to three to five years when the
pool of CS talent would shrink enough to start putting pressure back on employers for hiring.
The bad news is, is that if it's going to take three to five years for jobs to come
back and you just got laid off, that doesn't do you a lot of good, but it starts to give
you an idea about how to kind of think about where things are going to go.
Now that said, I do think things are going to be a little bit more complicated this time
around.
I personally have lived through the 2001 and the 2008 crashes, and there was kind of a
small crash at the early nineties as well, which is when I got in, CS was not considered
a growth thing necessarily.
It was sort of a thing that nerdy kids did.
And so what I want to do is talk about the, some of these structural changes that are
happening that I think might affect if and when the software development jobs come back.
And so the first thing that on that point that I want to talk to you is just to talk
about the term technology.
So even in the thumbnail, I said, when are the tech jobs going to come back?
And most people, I think, instinctively think of tech jobs as software development jobs,
but that's not strictly accurate.
That's actually a pretty recent, just a few decades phenomena that's been true.
For most of history, technology really just referred to the process of things getting
better.
And that kind of looks like two things, either means that things get cheaper or you have
new products and innovations, but you know, obviously things like hardware play a role.
And so we've kind of been emphasizing the software development side for quite some time.
And that's partly because the speed and the velocity with which someone could theoretically
get into the software development space and then have things go to the moon brings a lot
of attention and a lot of money.
The challenges is that it's not clear to me that the next few years, we're going to see
the same level of investment in traditional software development as a way to improve technology.
Some of that's kind of obvious because everybody's obviously so excited about AI and LLMs and
how that applies.
The one that's been catching my eye a lot lately has been a lot of investments in robotics.
Let's talk through that a little bit more.
If technology doesn't mean traditional software development, it means things getting cheaper
and faster.
We actually can see how that has affected the software industry itself over the last
few decades.
For example, back in the nineties, there were a lot of web developers who were just writing
HTML and that was a whole career and job.
Other roles that have been impacted like that over the last few years include things like
QA.
It used to be manual.
QA was a big thing.
Server management for IT.
A lot of people used to just manage individual servers where the server ratio might be 10
servers for a person and now that could be hundreds or thousands of cloud-based servers.
I've seen that affecting even the Java developers that I know.
A lot of them have, over the last few years, moved from I write a Java app to managing
Java apps, but you're also worrying a lot about things like managing your cloud clusters
or images and how you do the deploy or how do you tie an existing caching in with auth
to try to scale it out.
And so you're really doing a lot of data flow management, not necessarily writing Java code
all day long.
The theme that's underlying a lot of that has been up or out, right?
You either learn more and add more to your skill sets or at some point you get out of
the space.
So for example, QA.
Years ago, probably 15 years ago, most of the manual QA got kind of scrubbed out and
replaced with test automation and SDETs, for example.
So that kind of made everybody say either you're in and you're going to keep adding
more and more to your skill set or you're out.
One of the canaries in the coal mine for me around all the stuff has been watching how
AWS has evolved over the last few years.
Basically the dynamic is AWS can go to its customers and ask, what do you need?
And then that gets swapped out where what used to be manual developer work or DevOps
or what have you.
It just keeps moving more and more into off the shelf stuff that you can get from AWS.
The sort of last evolution of that even recently was probably some of these low code and no
code tools.
And a lot of those tools as a professional software engineer, you might look at and go,
well, that doesn't really do what I want it to do.
But if you can build an app with it that meets what you need, that's probably good enough.
And when I look on entrepreneurial forums, a lot of those guys are talking about things
like using no code tools to get their MVP launch.
So they're actually pushing back, trying to bring on a CTO type person because they want
to just get as far as they can validating their idea before they do a lot of software
engineering work.
Part of what's interesting about that is if you look at some of those tools, like for
example, here's flutter flow, which is a low code, no code tool that does mobile and web
app stuff.
They batted in an AI configuration so you can generate UIs and the snippets of code
that you need using an AI interactively.
Similarly, a super base, which is a Postgres managed service that provides a lot of extra
add ons.
They've added AI stuff right into their dashboard.
So part of the point there is that they're trying to lower the amount of work to get
things done, which is great, but it also means that the tech skills levels to be productive
with it shrink as well.
A lot of the entrepreneurs are using things like bubble or other platforms to just simply
build and launch their apps with drag and drop.
Remember, it's not about replacing all the jobs, but if we go through a few years where
every year it's five to 10% shrink in the overall jobs for a software development.
What that means is that we'll have a lot of price pressure on salaries and also negotiation
for the software engineering.
What that might look like is instead of six figure developer jobs, you get five figure
developer slash configuration jobs potentially.
So think about if you want to manage your website, you don't go hire a full blown high
end software engineer to update your WordPress site.
The other one is that a lot of the investment that I'm seeing right now isn't going to the
software developer space.
Part of this is because if the moats are low on software development, that means that as
an investor, you want to put your money in other places.
So obviously that might look like data.
If you want to build an LLM or provide other services, that might mean you're going to
put money into acquiring or managing large data sources and then crunching that.
And then the other one is robotics.
There's a term I've heard recently called dark factory.
The idea is that if you have enough automation in the factory, you can just turn the lights
off and then inputs come in, the robots do their thing and products roll out the other
side. If you're an investor, what do you put your money in?
Do you go build a new app?
What does that even mean?
What does that look like?
And especially if the moats are so low, given, you know, I can just build a lot of these
things. Or do you put your money into a new dark factory?
Right. And some of this stuff may be actually really good for us in the big scheme of
things. For example, I've been tracking and finding things like prefab housing, very
interesting where a factory can produce a house.
So what would it mean to deal with some of the housing crisis issues in the United
States if robotics and factory work is able to then allow us to dramatically decrease
the cost of new construction for folks?
Another example of this, Amazon just announced this huge investment in robotics and
that money is paired up with money from open AI, which is also paired up with all these
other huge sums.
So where this comes back is if you're a traditional software developer and you're
sitting there looking at this going, well, going from building rest services to doing
robotics is non-trivial.
Same thing with moving from I do rest services to I want to do data science.
So, again, that kind of comes back to, well, what or how are you going to invest in
building a skill set? In another video, I talked a little about some of the ways to get
a new job and how to think about your skill set and expanding it.
I don't know that I would say that like all the jobs are going to go away.
This is a thing that people are talking about now, but it's going to take years or
maybe a decade or more to deploy this stuff.
I don't know that the hype curve is going to really fall out the way that it's going to
wipe everything out.
But if you're looking at an environment where you're used to getting six figure work as
a software engineer and that might look like five figure work for the next three to five
years, that implicitly means a lot of changes in life and how we approach things.
Right. So anyway, I think that part of the point here is not to depress anybody, even
though that might be hard, especially if you just got let go.
But to kind of think about it as a we're all in very similar boats right now.
Right. Even if you have a job that you feel, you know, covers what you need today, the
risk and concern factors with all the layoffs and everything else should be cause for
concern. And when you're doing your planning, you need to think about whether or not those
roles doing it the way that you did it before are going to come back in the same way.
So pay a lot of attention to the job boards and what's going on.
And just also kind of think about at what point do you have a conversation about what the
future is going to look like for you in this environment?
What does it mean to be in a space where the jobs might just contract for five to 10
percent for the next three years?
Right. So with that in mind, I'm hoping to do more videos on this topic.
I do want to talk a little bit more about how the macroeconomic components interact in
with this and also some of the other options for folks that are currently doing software
development today.
But they kind of want to build some safety nets and some transition plans and things like
that. So I hope this was helpful for you and interesting.
Give you some food for thought.
All the usual things like and subscribe and all that fun stuff.
Thank you so much for your time and talk to you later.
