1. Something you’re at least vaguely interested in and don’t mind doing.
2. Something you’re at least vaguely interested in and don’t mind doing.
3. Blockchain, because it’s a scam that is rapidly disintegrating.

No one else can tell you what you should pursue. I didn’t know what I did or didn’t like until I tried a few things and figured out what aspects of them I like and what aspects were not for me. For instance, I don’t like frontend programming and I absolutely hate dealing with external clients. I do something more like data engineering, which a lot of people find deadly boring but I find perfectly satisfactory.

The other thing that’s been really important to me is decoupling my career from my self-worth. My job is not the most important thing about me. My job is something I do so I can get paid enough to do the things I actually want to do. I don’t need to LOVE my job. I need to like it enough to mostly not dislike having to do it 40 hours a week. For me this means I don’t find the work boring, I work with nice people, I mostly don’t have to do things I HATE (e.g. client presentations), and I’m not doing anything that conflicts with my values (e.g. I wouldn’t work on blockchain, or law enforcement projects).

1. It all depends on where you want to go. I used to work in an IT department where most of my coworkers had non-tech degrees. Heck I only have a 2 year degree in software development. I also know people with computer science degrees that can’t find jobs in the field. There really isn’t a best path here. Heck, a lot of folks in low level IT support roles are just people without much training, but an interest in computers.

2. It all depends on you. If you aren’t sure about something, maybe watch a few videos on a platform like PluralSight or Lynda.com. There are often labs or projects for you to start getting your hands dirty. Depending on where you live there might be places like FreeGeek that take volunteers to do support work, which in and of itself could get you a foot in the door of the tech industry. There are also a number of games on Steam that give you a rough idea of the work that each field entails.

3. Again, it depends on you. At this point in my life I’d avoid working for a FAANG (Facebook, Amazon, Apple, Netflix, Google) style company or a start-up. However, that’s not because there is anything inherently wrong with working for those types of companies, I just value my time outside of work.

The most important advice I can give is to try to meet people in the field. Locally you will likely have events called User Groups (you can look on Facebook or Meetup.com) where people who are interested in different technologies will share what they know. Get to know people. Ask questions even if you think they’re obvious or dumb. Tech skills will help you keep a job, soft skills will help you get a job.

Oh where to begin?!

Okay. Find out what you love doing and learn it. Every career is going to have some kind of need for tech workers.

I have a bachelor’s and master’s in computer science and a master’s in anthropology. Having something that you really enjoy allows you to gain domain knowledge. If you’re passionate about this and about tech, then you’ll learn a ton of stuff on your own through sheer love of the topics.

Depending on your age, you may also want to do some introspection. I started my undergraduate studies in physics and realized I had way more fun writing the simulation software than with the actual subject. But I had no idea what I actually wanted to do until I was around 23 and had gained enough experience as to what to expect for each field.

Degree programs in computer science are intense. There’s a ton of math, though every day I’m happy that I paid attention in linear algebra. And the electrical engineering courses are still invaluable for my hobbyist projects.

• Degree: Anything in engineering is ideal. Computer science is also fantastic if you think you can handle the course load. I’ve seen amazing systems architects with degrees in Russian literature and shitty programmers with degrees in CS.

• Fields: These are nebulous. Infosec is probably the most misunderstood. There are very few hoodies and Guy Fawkes masks. There is, however, more paperwork for a major pen test than there is for a mortgage. DevOps is where I landed and couldn’t imagine being anywhere else. Network admins are the drummers of the IT world; nobody is sure what they do, but we know that they’re important.

• Avoidance: The gaming industry. Long hours, insane deadlines, and middling pay. The financial sector is soul crushing. (I quit a job there without a landing spot simply because I couldn’t deal with how badly we were fucking over consumers).

More opinionated: AI is a bubble that will pop. Getting a job in that field is easy right now. But the knowledge required to advance in that field is an order of magnitude higher than most people expect. And the math involved is not something that most people can “pick up” on the job.

Edit:

Learn, master, and love Linux. For people trying to get into the tech field there is no better advice. The world runs on Linux. If you want to do pen testing, operations, server administration, etc. then skills here are not optional. Even environments that are nominally Windows will almost always use Linux systems on their edges.

Python is a great general purpose language to learn. Vi(m) is also good to learn. Not for text editing, but Vim dueling is our version of a street fight.

Computers and technology are so commonplace now that kids are growing up with enough skills to work a help desk, so I’d avoid support jobs except to get your foot in the door of something bigger, or to make money while studying, etc.

If I was going to do it again, I would have learned to code because that’s where the explosive growth was. Not sure it will be that way going forward, but there will always be a need for good engineers. That being said, if I was going to get paid to code, I would want to get PAID to code, so I’d be looking for something incredibly niche, like COBOL for example. I knew somebody who wrote assembly for aerospace and had some of their work in orbit. Pretty cool.

Avoid consulting companies that promise you Senior positions while you are a Junior.

They’ll teach you a language and platform then ship you out B2B with a fake resume and social, including references and experience (they even provide support while you’re on the job).

It sounds like a great deal if you don’t have a job, need a job, and have the right skill set but these agencies make a killing off of either inflating desired salaries or skimming more off of yours to recoup.

Shit is so bad they fly people across the country for training who then work at $130k+ jobs straight out of a coding boot camp without a degree.

There are some legit companies that train developers and help them find jobs but there is a lot of immoral activity that takes place.

• A good GitHub/GitLab code project portfolio will get you a job in software without paying for a degree. My degrees are in biological sciences and I’ve worked with people who haven’t gone to university or have liberal arts degrees (esp English and philosophy)
• The first gig is the hardest step. Companies hate hiring folks without professional software experience. Sometimes you gotta take that shitty, short, and low-paying contract
• IMHO the best advice from boot camps is to attend local tech meetups, ask for informational interviews, and assemble a portfolio of personal projects
• A good recruiter is gold; unfortunately, most are a combination of confabulation, idiocy, and chicanery
• if you’re driven and sharp, QA/support can be good entry points to engineering

For me, I went to school for computer information technology (System administration) and computer sciences (software engineering). I am now 10 years into being a game developer. I made fun of a lot of people who got into comp sci just to be a game developer because I believed if you didn’t love coding itself then making a game was going to be a huge pain. And all of those people dropped out of comp sci before our final class.

My first job, was at ThePlatform For Media, Inc. (Comcast Subsidiary that did all the VoD streaming) as an Application Support Engineer. Basically, I told real developers how to use the API and tools we had our engineers set up. I was an engineer middle-man. I went from that to T-Mobile HQ as a Product Realization Engineer. Basically, I matched the technology we had with the market and resources we had to build tools that helped us… Yawn… sorry I… Anyways, I built software to help bill customers easier. Fucking BORING.

This is why I got into games. Games aren’t boring. They bring meaning to the code I write. I know why I am writing the code. There is strong reasoning behind it. I work with designers to make systems that have meaning and impact on the artwork we are making and delivering. That’s very motivating.

So find something you like doing, find a field that gives you a strong reason to do what you like to do.

What should you avoid? Avoid not using pieces of technology because someone you don’t like contributes or benefits from them. An example of this could be something like Twitter or Windows or such. You might want to say “Well I shouldn’t use X because Y person sucks and I don’t want to give them money.” While this is typically smart and what I would agree with, it usually comes with an issue. “The alternative is terrible and slows down my productivity but at least I am not giving money to people I hate.” This is the wrong mindset. Be as productive as you can be first. Only switch to something when you feel you can make that sacrifice in being productive. At the end of the day, we still live in a capitalistic society and there is no ethical consumption under capitalism at this point. The ethical thing is to actually be productive as possible then cut time out to be unproductive as you switch, potentially raising awareness as you do so because you’ve been able to be productive. So know what you are losing by switching to an alternative that makes you less productive.

Do it because you love it. Not just for the money. Takes a lot of work and more then 40 hour weeks. Good money but not easy money.

First thing I would do is try to figure out what you enjoy doing. Bit-fiddling and getting really low level? Web dev (and breaking that one down, front end, back end, dev ops, etc.)?

For cyber security, a lot of others here have mentioned it, but definitely wanna echo: learning Linux is key. Also get familiar with networking, routing, switching, etc. Understanding databases is really good because it’ll help you understand how they can be exploited in various applications.

Degree:

It used to be it HAD to be CS and nothing else. But these days, it seems like most jobs are happy with any tech-adjacent degree as long as you can prove your stuff.

But along the way, start building small projects on the side as you’re learning. Build up to more complex ones. Course work alone won’t teach you enough. Most degrees will have some sort of senior capstone project that will be good for experience as well.

If you’re doing cyber security/infosec there’s various options. Some schools will have dedicated infosec degrees, where others you can pick to major in CS or IT.

But after your first couple of jobs and getting a few years of experience, the degree you have shouldn’t matter to employers anymore.

Field:

Depends on what you want to do, really.

Avoid:

Games: It’s a nightmare, and no matter how much you love the work, the industry will chew you up and spit you out.

Fintech: It’s shitty and exploitative of it’s customers.

AI/ML/Crypto/Blockchain/etc: These are full of empty buzzwords with either vaporware, or products that cause far more harm than good.

deleted by creator