You’re in the wrong field, my man. I sit at a chair 60 hours a week staring into a empty void that is my monitor. Wait, maybe we are not really that different after all.
I just really don’t know how to get in, while living in central Florida, with no degree, while not taking a pay cut which I can’t afford as the sole earner in my household :/
If you’re thinking about shifting careers, I’ve been there. I started as a self-learner with no degree, before the ease of joining a freelance service was a thing. My starting point was a small firm where I did tech support for the coders. I got involved in automation projects and gradually built trust by proving I could deliver what I promised.
I think that the core principles I learned remain valid today: Learn by doing projects, learn in public, and be patient.
If I was starting again, and if I didn’t have a job next to the right people, I’d probably do the following. Start with creating useful projects. Treat these as opportunities to learn and simulate real job conditions. If your work involves coding, share it on GitHub. If it’s about building infrastructure, treat it as Infrastructure as Code and share it on GitHub. If it’s not code-related, or even if it is, document your work and what you’ve learned on a blog.
Regardless of your project’s nature, make sure to record your learnings and pass on your knowledge. It helps reinforce your understanding and it gives you something to point to during interviews.
You’re in the wrong field, my man. I sit at a chair 60 hours a week staring into a empty void that is my monitor. Wait, maybe we are not really that different after all.
I just really don’t know how to get in, while living in central Florida, with no degree, while not taking a pay cut which I can’t afford as the sole earner in my household :/
If you’re thinking about shifting careers, I’ve been there. I started as a self-learner with no degree, before the ease of joining a freelance service was a thing. My starting point was a small firm where I did tech support for the coders. I got involved in automation projects and gradually built trust by proving I could deliver what I promised.
I think that the core principles I learned remain valid today: Learn by doing projects, learn in public, and be patient.
If I was starting again, and if I didn’t have a job next to the right people, I’d probably do the following. Start with creating useful projects. Treat these as opportunities to learn and simulate real job conditions. If your work involves coding, share it on GitHub. If it’s about building infrastructure, treat it as Infrastructure as Code and share it on GitHub. If it’s not code-related, or even if it is, document your work and what you’ve learned on a blog.
Regardless of your project’s nature, make sure to record your learnings and pass on your knowledge. It helps reinforce your understanding and it gives you something to point to during interviews.