Ask HN: Is “learn to code” now “learn to drive a big rig”?

38 points by leet_thow ↗ HN
We are all familiar with the layoffs in the tech sector. Will the people who have been laid off eventually have to find other avenues for employment in sectors of the economy where hiring is still strong?

92 comments

[ 6.3 ms ] story [ 177 ms ] thread
If anything I think those being laid off right now will be sought after in areas that want tech sector quality but have not been able pay tech sector wages. Government jobs, education, nonprofits, all have lots of openings right now.
There's also a very long tail of businesses that are not "big tech", but still have significant IT departments and pay well for "boring" work.
That's my impression as well. I don't understand the perspective of "is software engineering over because I can't make a quarter million base salary anymore?". I've always preferred smaller companies and never wanted to work at a large tech company - don't foresee much change in my future unless I willingly change industries for personal reasons
Yeah I mean what's so bad about half that pay and living somewhere affordable?
(comment deleted)
Expect they don’t pay all that well. Just ok ish
I have trouble buying this, having seen the salaries being offered by local government agencies looking for devs. I guess if the layoffs depress wages across the board some of it might start to look a _little_ more reasonable, but even in a market that's nowhere near the insanity of big tech salaries, the government salaries on offer are laughably low.
I know people that work in tech at decent companies that can't buy a house.

Every non major metro area mechanic, school teacher, city employee I know has a nice home.

People should really consider doing lower paying boring work in places your mortgage can be $2000 a month.

>places your mortgage can be $2000 a month.

This is shockingly major metro-area-centric. I want you to know that, and I feel like people on this board really need to understand how HIGH urban and suburban costs are.

In many areas of the country, $2000/month is a seriously frighteningly massive home. For reference - in the middle of rural flyover, our 4 bedroom, 2.5 bathroom, 1800 square foot, full basement, 2 car garage, 1100 square foot full workshop home mortgage is 15 years at $750/month. We pay that, plus another $400 /month for the 70 acres the home sits on as well.

I don’t think that’s still true.

In Spokane, WA 10-15 years ago you could get starter homes for under $100k. Now that price is at least $300k (after cooling off for the last 12 months).

If interest rates hadn’t risen it might be somewhere in between though.

My 1911, 3br/1ba in-city Spokane house cost me about $90K in 2003, currently appraised+taxed at around $300K as you say. I've no idea how ordinary people [that is, those w/o high incomes and/or high levels of wealth], and especially renters, are getting by. From what I read in it the local forums and see at the food bank every week, a lot aren't getting by.
OPs comment is true of minor metro areas as well from what I’ve seen. For example, Spokane, WA.
Yikes, even $2k is a lot more than what I'm paying. Living in a city has its benefits but RIP bank account.
Est. payment: $1,601/mo, 4bd, 2ba, 2,478 sq. ft. -- https://www.zillow.com/homedetails/801-14th-St-Stanton-NE-68...

Est. payment: $953/mo, 3bd, 2ba, 3,192 sq. ft., 1.31 acres -- https://www.zillow.com/homedetails/1950-River-Rd-Forest-City...

Est. payment: $1,097/mo, 3bd, 2ba, 2,326 sq. ft. -- https://www.zillow.com/homedetails/301-S-Warren-St-Watertown...

Est. payment: $1,139/mo, 4bd, 2ba, 2,148 sq. ft. -- https://www.zillow.com/homedetails/522-Clifty-St-Harriman-TN...

Est. payment: $887/mo, 4bd, 2ba, 3,123 sq. ft. -- https://www.zillow.com/homedetails/172-Nebraska-Ave-SW-Huron...

Est. payment: $1,107/mo, 3bd, 2ba, 2,957 sq. ft. -- https://www.zillow.com/homedetails/415-W-Parrish-Ave-Owensbo...

I have a friend who is basically an extremely "toxic capitalist" (to put it simply).

He "called" that it wouldn't last that a lot of people were making "big" tech money + not really working 8 hours a day.

Maybe that's what this whole "big tech layoff" is. A reset to lower overheated wages. Make 500,000 unemployed programmers compete for paycuts.

(comment deleted)
Not quite sure why you're getting downvoted. Might be due to your friend's unsubstantiated claim tech workers (on average) are overpaid while underdelivering. However, the core observation is reasonable. Layoffs create desperation in the labor pool which is likely to drive median tech wages down. This benefits companies opex long-term as they restart the hiring cycle over the next couple quarters. Doubtful we're seeing market-wide collusion on these layoffs but it certainly creates an institutional hiring advantage.
Agreed but also it’s weird how a lot of lay-off %s are 7% +\-1 though?
It's like one CEO did it and it opened the door for it to be socially acceptable climate wise for everybody to follow suit.
So, a fad?
I would say fad is probably a poor choice of words given the perspective "if one CEO thought it was appropriate (they let headcount + salaries creep up too high" and deemed it was in the realm of "action needed to correct", it probably wasn't baseless.

Have you taken a look at the year over year headcount growth of some of these companies? If anything, you could make the argument that 7% isn't enough :/

I’m not really in the business of sympathizing with CEOs for poor past decisions
> Might be due to your friend's unsubstantiated claim tech workers

In his defense, he does own a small tech startup ($1m/yr I think?) and that has like 10 employees (3-4 engineers), so he has his finger on the pulse (or at least he thinks he does) when it comes to tech hiring.

That's a big problem, right? You think his claims are unsubstantiated, he thinks he knows it all and he's seen it with his own eyes. Who is telling the truth?

Your friend has bought into the hype, as a lot of people have. There are very few people making "big tech money" who are not also putting in very long hours. They exist, but are often/usually in the (long) process of being "managed out."

There's no doubt in my mind that a lot of this is a power-play by profitable companies to push back against developers who've collectively gained more power at the negotiating table. Paying dividends and doing stock buybacks while saying "tough economic headwinds require us to lay off 6-8% of you" can only be a power move, as far as I'm concerned.

Dividends/buy-backs and layoffs are derived from the same concept. The company has excess resources they do not plan to use in the future. If you have excess cash, return it to the shareholder. If you have excess employees, reduce head count. It means the company doesn't want to build anything at the moment (for various reasons include prep for a downturn).
> The idea of comparing the expected return from a project to a risk-free rate, such as the return on a Treasury bond, is a common method used in finance to assess the riskiness of an investment. This is known as the cost of capital, which represents the minimum rate of return that an investment must generate to be considered economically viable.

How would you breakdown the distribution of projects inside of Apple from a return perspective?

Some will be 0% or negative due to R&D.

Some will be massively profitable (net 20-40% margins).

How do you decide what the right amount of loss-leading R&D projects to have is?

When companies trying to make cost cuts see an employee making $500k I don't think they go 'oh that's okay because they're working long hours'.
If you're a coder you get to sleep in your own bed.
If you've got a fancy rig, your bed comes with you.
I can't say I've ever wanted to work as a trucker, but I have wanted to give a sleeper cab a try at least once in my life, just to see what it's like.
Are these two points basically true?

> As time goes on, businesses are continuing to rely on more software, not less software.

> AI tools are very fascinating, but are nowhere near ready to replace most programmers for most tasks.

If those points are true enough, developers as a group aren't going away, though some individuals might choose a different path.

More and more software does not necessarily require more and more developers to write it.
There's plenty of low code / no code solutions right now and somehow programmers are still trucking along (pun intended).
Not to mention someone has to code the no code tool, alongside all the plugins, scripts and glue code that at some point will be required.
Even with low code tools the percentage of people who will develop the tool will be low compared to the number of users.
No code is just "code with a fancy UI, a less powerful language and no or bad integration with common tooling".

It doesn't replace programming, it _is_ programming. It's useful because it makes programming more accessible and in some cases the visual representation has benefits over text.

I see more and more professional fields and application interfaces adopting things like SQL, Python, Notebooks (Jupyter etc.), JavaScript etc. Excel is obviously huge. A ton of technicians that work with physical stuff are also writing code in embedded interfaces or on large screens even. Programming is not a thing only software developers do.

Software developers are often more like solutions specialists who's tool is software, you would need the same skillsets to solve business problems with lowcode, but code is at this point still the tool of choice for those teams of solutions specialists.

Think of it this way, even if it were possible to run an enterprise through lowcode tools, an enterprise would still hire an agency or consulting firm to build it, and so the decision of what tools to use still goes to the specialists.

> More and more software does not necessarily require more and more developers to write it.

It has so far. We might have expected the massive gains in developer productivity over the last 70 years to have resulted in the demand for new developers slowing down at some point, but it hasn't. In a very typical way, more supply just gets eaten up by more demand - if at any point we can afford to have fewer developers, we'll just end up writing even more software with the excess capacity.

It's hard to imagine a point of diminishing returns on software, since it's so useful in basically every walk of life.

> It has so far. We might have expected the massive gains in developer productivity over the last 70 years to have resulted in the demand for new developers slowing down at some point, but it hasn't.

Recently there has been an explosive transformation from software as a user and productivity focused industry into an adtech one, which has increased demand temporarily.

> In a very typical way, more supply just gets eaten up by more demand

Sure, but increasing supply also means decreasing price by that same model. Decreasing price means less money for developers, meaning less people are incentivized to become developers, leading to equilibrium. Of course, that's a very simplistic model.

I know its not equivalent, but a really simple human can learn to drive and self driving cars haven't mastered that. I don't think its the case that a really simple human can learn to code. since that is harder than self driving, and ML still cant self drive, I am not worried yet.
> I don't think its the case that a really simple human can learn to code.

People always think this about their own trade. But let me assure you that I am dumb as shit and a pretty decent programmer as well. I've taught programming to beginner adults, who were coming out of prison or the military, and out of hundreds I ran across maybe a handful that truly truly were not ever going to be able to learn it to competence.

The main skill at play from my experience is comfort with the state of not having a clue, and tolerance for frustration. That's an uncomfortable emotional zone for work; people will frequently abandon the pursuit. But that doesn't mean they can't learn it.

It's like playing a violin or something: you could, anyone could if they put the hundreds of hours in. Who does put those hours in may be a self-selecting group, but it doesn't mean there's anything inherent in the skill itself that limits who can learn it.

Yup. This.

Programming is not special knowledge or technique wise. It’s having a super high tolerance to frustration and somewhat lesser to being comfortable not knowing a solution.

You're right that having the capacity to program isn't about having special knowledge, but it's not about tolerance to frustration. It's about the ability to think in abstract terms and being able to mentally process an abstract mental model consistently.

Even a person with far below average intelligence can do many things in physical space with enough training. They can be shown how to set a table for a fancy banquet, can physically understand what a knife/fork/spoon/plate/napkin/cup are, their relationship in physical space, and eventually learn to set a table as instructed with enough training and practice.

But there's no amount of training that works to help a dumb person understand abstract problems in programming. Things like understanding a variable represents something, you have many variables to keep track of that all represent different things, and working through the logic of even a simple function in a program that changes those variables are beyond dumb people. I wish this wasn't the case, but it's reality.

giraffe_lady is being too humble if she's a decent coder and genuinely thinks she's dumb. There is no such thing as a dumb coder: it's a complete contradiction. In reality, I'd bet that almost everybody on HN who seriously uses this site to discuss ideas is at least in the top 15% of IQ for their population group.

The frustration part is about how different (than a person) computers make you think and how unforgiving computers are to even the smallest errors.
Didn't you answer yourself? Having a high tolerance for frustration.

That's surprisingly rare from my personal experience.

Also, I don't tolerate frustration on a personal level as much as I would like but I'm really good at tolerating computers. Weird.

I’d rather learn a trade like plumbing or electrical systems. Hell, the richest guy I’ve ever met ran a high-end masonry business.
The nice thing about masonry is it's a skillset that never ages out. Not as long as entropy exists.
Go hang out with some older tradies.

It absolutely wrecks you body. You can make a decent living, but it isn't the easy money that a lot of people think. A lot of the older tradies I know made sure that their kids went to college if that tells you anything

Yes, if going this route, would be optimal if you own your own business so that over time you can hire help and just manage the business.
You gotta get out of doing the work yourself as quickly as possible, it's a young man's game and if you've got the smarts you start your own business to avoid having to do 100% of the manual work yourself.
I suspect you mean "owned" by ran.

Trades are a decent entry into owning a small business with higher barrier to entry than say a restaurant but still pretty straightforward and can be made revenue stable with a small team (sometimes no permanent team, e.g. some builders). Especially if you grind when you and the business are young, you can end up in a good place fairly predictably.

But mostly people are financially successful here mostly by being business people, not trades people - with all that implies. Sure, there are some people who do well in a strong union, but it's a small fraction of the market.

Many people actually working a job the trades are more likely to end up with health problems and a sketchy retirement outlook.

In many places if you run a (small) business _well_ that does craft stuff like plumbing, electricity and similar, you're going to have people lining up for your services to no end.

I don't know why that is. But I assume that the combination of excellent trade/craftsmanship and organizational skills is very attractive.

I always hear the same story from my friends who have been working in small service businesses, whether they are gardeners, carpenters, electricians or cleaners etc:

When it's bad (fairly typical) it's the boss being stretched too thin between too many responsibilities, or its a person that has no clue about the actual trade. They are the both the bottleneck for solutions and the cause of compounding issues.

It ends up in overworked, stressed workers, missed deadlines and mistakes that snowball into more such problems.

A trade/service business that is run well, treats their workers well (which is their major asset) and does good work can charge more and will never run out of work. It seems there is no simple formula for this so you end up with a lot of what you describe above.

"I don't know why that is. But I assume that the combination of excellent trade/craftsmanship and organizational skills is very attractive."

This. I'd say at least 25% lack one or the other. So many end up so over budget, very behind schedule, and do substandard or sloppy work.

What exactly are the equivalencies between coding and driving a truck - is it supposed to relate an industry potentially ripe for automation or just an "expected" service many people rely on?

I find this all hilarious because just like 5 years ago so many were quoting Bill Gates saying "programming knowledge will be the literacy of the 21st century" and it depends. If people are all so genuinely interested in tech and coding in the first place what's the problem?

Not so much that the jobs are inherently similar. It's more that, during the last recession roughly 15 years ago, and IIRC actually the past several recessions, there were a lot of ads for truck-driving schools in the media. The idea is that trucking is supposed to be a recession-proof trade, and whether that idea is true or not, it's good for trucking schools if people believe that. The parallels to coding, bootcamps, etc. are clear.
Gotcha, thanks for clarifying - it's about the Utility of the lines of work.

I personally feel better about thinking of these lines of works as "very important to maintaining the status quo" rather than "recession-proof" but it's basically the same thing

Learn to X is always the dumpest way to go about fixing labor shortages. I don't want to know how many 2X year olds will burn out coding just because they actually loath it. If the pay goes down there will be an exodus.
100% accurate. I've worked in higher education for years, and it's a constant drum beat of chasing a world that doesn't exist.

20 years ago, it was just all about going to college. Go to college. Get a degree. Get a good job. That was the path.

10 years ago it became, go to college, but pick the right major. Finish that major. Get a good job.

5 years ago it became, go to college and major in engineering or cs. Finish those majors. Make money.

For the last year or two, it has really been all about trades. Welding, plumbing, HVAC, electrical.

It's just a matter of time before those graduates can't get jobs and it swings again. I'm betting ethics and philosophy and/or social work will be the next big push.

The current state of the economy is not the permanent state of the economy. Many tech workers will see new opportunities, though not necessarily soon enough to stave off real hardships.

That being the case, there is no harm in learning another way to make a living. Having a fallback is always a good idea. If it becomes the main thing because your first career never came back, count yourself lucky and go with it.

Trades are a great idea.

... I don't think I'd specifically recommend "Learn to drive a big rig" though. In addition to the industry itself being a real bad deal for vehicle operators (https://www.nytimes.com/2022/02/09/business/truck-driver-sho...), it's the segment of the transportation sector centered in the crosshairs of disruption-through-automation.

The self-driving vehicle companies that laid off were, broadly speaking, the ones working on individual vehicles and taxi services, not the ones working on self-driving trucks. That sector is still going strong because the value proposition is simple and obvious (lives saved and money saved per mile).

Trades are an okay idea. People have this rosy picture of a skilled trades job, with high pay, great benefits, and security from a strong union.

And while that can be true, it is certainly only a very small part of the picture. You can't just say, I'm going to be a plumber, and bam, you're a plumber. You could, conceivably do that with something like rough frame carpentry, but those aren't the high paid trades people talk about. Most trades have required education and/or apprenticeships that aren't paid that great. If you can make it through that, then the pay gets better. But we're talking years, literally years to get there.

Then, once you're doing the skilled trade, you're working long (looooong) hours, long weeks, away from family (sometimes), in the heat and cold and rain.

These are good jobs, but they're not magic make money jobs like people tend to frame them. They're hard, and your career will get cut shorter than it should by either straight up injury or problems of accrued physical debt from repetitive strain.

Ask a plumber to show you their crawlsuit and describe the last month or so of their work and you being to appreciate their rates.
I talked to 3 plumbers recently when I bought a partially built house. First guy was a "commercial" plumber working on new builds only. Second guy was a "home renovation" plumber. Both these 2 plumbers won't go near a clogged toilet. Third guy specialized on clogged pipes and home emergency repair.
> Third guy specialized on clogged pipes and home emergency repair.

And knows anyone calling him is likely over a barrel and willing to pay big money to make the problem go away. Odd hours, but a respectable hourly rate (assuming he has some skin in the game vis-a-vis owning the business).

Talk to a tradie who was around in 2008.

Ask an older tradie how their body is doing.

Ask a tradie how often clients don't pay their bills.

Ask a tradie how many paid sick days they get.

The trades are one way to make a living wage, but they definitely aren't an easy way to do it. There are some union jobs, but largely the trades require you to run your own business in one way or another. Even your average car mechanic employed by a garage has to provide their own tools at HUGE cost.

I think a lot of people don't realize just how hard it is to be in the trades.

"Just be an electrician! Look how well they're paid!"

Sure, be an electrician. But first try working an 8-hour day with your arms above shoulder level half the time.

Show me a sparkie that only works an 8 hour day, it's 12 hours standing on cold concrete.
Yeah it’s not the 8 hour days that you are thinking of. Blue collar workers work terrible hours and have mostly been robbed of holidays and weekends
The ones who make Real Money in the trades are mostly in sales & management before their career's too far along (either very high-up in some larger firm, or running their own thing with employees). Their knees tend to be OK.

[EDIT] Actually, that kinda goes for tech workers who aren't in the top part of the trimodal comp graph, too. You either move into management or start your own thing, if you want Real Money (else you'll see a bad mid-career plateau).

(comment deleted)
I have actually looked at a CDL out of curiosity. I can't imagine not getting a CDL right now because of automation. I think this is a much harder problem than it seems at the edges, especially in poor winter conditions. Most people would get sick of trucking before they are automated to the unemployment line.

The bigger issue really is that trucking is a bad deal. Super dangerous job that doesn't pay much of anything for the hours worked while your health is basically destroyed from sitting.

Stories from new big rig drivers are pretty terrifying. It sounds like the first year is spent hoping everyday that you don't kill someone as you learn to handle this 80,000lb monstrosity.

I think it's probably inevitable that software development becomes another trade, or at least becomes less of a career hack — a fairly simple way to make an outsized amount of money given the rareness of the skill required. I don't know about the timeline for this happening, but I think it has to happen sooner or later.

I think it would be a mistake to switch to trucking right now, as despite delays with no end in sight, it does feel like some substantial use of automated driving in the commercial driving industry is coming eventually. I would expect that to reduce the market value of drivers. If someone wanted to become a truck driver, I'd say he'd better do it for the love rather than the money. Even though both careers are going to get shaken up, it's still a lot easier to make six figures in software for now.

In general, I roll my eyes when politicians suggest that people who lose their jobs due to industries shifting out from under them can just go learn new skills and get back on track. I haven't seen that happen. It feels like a pat on the back as you're shoving them out the door.

The recent layoffs are part of a business cycle that we're currently going through. Sooner or later the pendulum will swing the other way and tech companies will be hiring for high growth rate again. I guess this is the first experience of a business cycle for a lot of people in the tech sector, hence the collective "surprised Pikachu face" as the kids would say.
my sister drives a big rig, and my nephew use to do it. Not only is it an extremely cyclical industry, its not for everyone. you have less social life and spend more time sitting than a coder.

One port change can cause truck routes to disappear. also simple routes will probably be replaced by self driving rigs in the future. I would highly not recommend lots of people jumping into that.

however, if this tech rekt lasts, I imagine people will be flocking to the next big thing until that crashes too. its like bulls on ice

Nope.

I know I'm not the only one here who didn't enter tech immediately after college. Once upon a time I was an electrician. I've done framing, roofing, general farm work, I was a pharmacy technician and ran a photo processing lab. My hobbies today include things like machining.

The "problem" in tech isn't so much the availability of jobs, but the relative income. There's nothing I've found that I could do that would replace my income in a reasonable time frame. If I left tech I'd be looking at a >50% reduction in income.

Former CDL-A driver here. I fell for the truck driving meme back in 09 when the economy shat the bed, I thought it would be a relatively easy way to earn 50 to 60k per year without any college degree. I was for the most part wrong. The companies lie to get you in the drivers seat, lied about CPM, lied about sign on bonuses and hometime. When it was all said and done i was making roughly $200 more per week driving a truck than i was working retail at walmart, and at least i got to go home and sleep in my own bed.
Truck driving is frictional. The management that screwed up something as obvious and profitable as railroads created a frictional desire for diesel trucking to work around their mistakes.

Likewise, strangely, coding is also frictional. The business people who could "write their own code in COBOL" or "write their entire business in excel spreadsheets" would already be programmers if they could program which they can't so they don't AND management will not be up to the task of deploying profitable AI, so coders also have guaranteed work.

To some extent, labor only exists via mismanagement of capital. Humans CLEARLY aren't capable of properly managing a rail logistical infrastructure, so truck drivers have permanent employment. I would theorize that humans aren't capable of deploying AI generated programs, we've barely been able to deploy code written by competent humans, so coders should have permanent employment.

This is a deeply flawed premise. Tech sector grew headcount by like 100% over a couple years, and then did layoffs of 5-10%. They still have massively more employees today than they did pre-covid.

People are significantly overreacting to the current layoffs and ignoring all the massive hiring spree of the last 3 years. If you hire 100 people and then layoff 8, the narrative shouldn't be that the end is nigh.

In the sense that people looking for a new career will move towards non-tech paths instead - hell no. These layoffs are minor.

I think the opposite will become increasingly true: folks that otherwise would not be found in a computer science/engineering undergraduate will find their way to tech.

Software/Tech is incredibly wide and deep. There's need all over the stack, and there is definitely lots of need at the medium-skill level. I spend a lot of time configuring AWS, and running simple db queries. Look at the heaps of programmers who are economically successful in a single framework like React.

I think the field will stratify and there's lots of room in the 50-80k/y range doing useful tech work for businesses in every sector. I can see it in FAANG where there's a clear distinction between those destined for Staff level and invent new things, and those who will plateau at SDE2 but do so much necessary work.

No, "learn to code" is now "learn to read".

Long ago, people could get work as a scribe or scrivener -- knowing how to read and write was, on its own, enough to get you a job. As literacy became more prevalent, it wasn't enough to "just read". You had to "read and ____". Similar to business; I would not recommend someone get "just a business degree" so they can apply to any company in the world. I'd recommend they get a "business degree and ____" to target a specific industry or role.

The same is slowly happening with programming. As the spectrum of what "programming" means continues to widen, and as code-literacy becomes more and more common, it's going to be harder to get a job as "just a programmer". So learn to code, And.

While some stuff is slowly becoming more accessible, the deeper end of technology gets deeper and deeper - complex systems with many moving parts operating on many different levels of abstraction.
I'm not sure about these comparisons because even with more and more people learning scripting and/or a few DSLs for their industries Software Engineering is still a career. Deeper knowledge and experience matters.
You need to work with some Gen. A or whatever comes after gen z.

They have a level of computer literacy that is shockingly bad. They use computers everyday, but only within the walled gardens of google classroom/iOs/Android.

I taught an after school HTML/CSS for grade school age kids, and the majority of them didn't know about the concept of a directory structure. Even just saving a text file (instead of having a file autosave to their google drive) was a foreign concept.

Kids these days very much are NOT digital natives in the way that millenials and Gen x were.

What is really troubling is that many kids are impatient with technology (thank tiktok and other apps for that) so coding is the worst they could imagine.
It seems that programming on any heavily used platforms will eventually come down to quality and price. I have seen that when the bosses see that the quality of the software can be managed at a lower level (quality being lower) then the software jobs will go to the lowest price. With remote working now stable and accepted, the software jobs will go to a job market that is cheaper. Also when you factor in tools that are able to create software for users by users just describing what they want and the users can update the requirements themselves, software jobs will evaporate quickly. Writing software will go by the wayside as a career. There will always be exceptions like, platforms that are not as popular, hardware software, specialty software, etc. Time now to start thinking about security in your job and learning skills that will keep a paycheck coming in.
Honestly as a senior engineer at a FAANG like startup, coding is but a small part. Most of my week is split across

- coding

- architecting systems (if we're in the design phase of a project)

- writing design documentation

- researching business requirements (basically understanding the domain i'm working in)

- getting cross org support for my work and meeting stake holders

So yeah for most tech roles nowadays, learn to code is the equivalent of learn to send an email. I think the days are numbered for developers who just want a bunch of Jira tickets given to them and be left alone.

Layoffs in the tech sector are happening now, but won't be happening forever. The world is relying on more software, not less. Understanding programming will still be valuable in the future.

Also, just a note on the specific comparison: it's a lot easier to learn to code in one's spare time than to learn to drive a big rig. Learning to code is free, and can remain free until you ship your first product. The same is not true for most other career choices.