changing carrers as a 34 y/o man in nyc
I've been into coding for as long as I can remember. Even though I've never worked professionally as a software engineer, tech has always been a huge part of my life. I was fortunate enough to always be good with my money, and if I ever needed help, my mom had my back (which honestly wasn't often). Because of that, I never felt forced to jump into the first coding job I could find.
I've worked in non-tech jobs my whole life, but I was always the person everyone came to when something tech-related broke or needed to be figured out.
During the pandemic, I paid out of pocket to attend the Rutgers Coding Bootcamp. Looking back, that bootcamp was the icing on the cake. I had already been teaching myself for years, but after finishing it, everything just clicked. My JavaScript improved dramatically, I became a stronger programmer overall, and even data structures and algorithms started making a lot more sense.
Then ChatGPT came along, and that changed the way I learned even more. Instead of getting generic Google results, I could ask follow-up questions, dive deeper into concepts, and actually have conversations about programming. It became one of the best learning tools I've ever used.
The moment I realized I'd come a long way was when I started talking with other developers. I've had conversations with people who have been in the industry for several years and with people who had just graduated. Sometimes I was teaching them concepts they hadn't seen before, and other times I was learning from them. Those conversations made me realize I actually knew a lot more than I gave myself credit for.
This Fourth of July weekend, I found myself watching AWS tutorials and cloud engineering project videos on YouTube because I'm trying to break into cloud engineering and DevOps. Somewhere in the middle of those videos, I realized something: I genuinely love learning this stuff. Whether it's AWS, backend development, networking, or software architecture, I enjoy figuring out how everything works.
I'll be honest, frontend development has never been my favorite. I can do it, and I've gotten pretty good at it over the years, but backend, cloud, infrastructure, and system design are what really keep me interested.
This weekend alone, I built two AWS-focused projects:
- A Dropbox-style cloud storage application using Amazon S3 with secure file uploads and downloads, along with a React/Next.js frontend.
- A production-style AWS networking project with a custom VPC, public and private subnets, security groups, IAM roles, and a foundation that's ready to grow into a larger cloud architecture.
Right now I'm working on adding database support so uploaded files can have metadata stored instead of relying only on S3. I'm thinking about integrating PostgreSQL or DynamoDB, adding user authentication, file ownership, sharing permissions, presigned URLs, logging, monitoring with CloudWatch, and eventually deploying everything with Docker, Terraform, and a CI/CD pipeline.
I'd love to hear from people already working in cloud or DevOps. If this were your portfolio project, what would you add next to make it stand out to recruiters or hiring managers? Is there anything you'd expect to see in a production-ready cloud application that I'm missing?
It honestly reminded me why I started coding in the first place. I don't just enjoy writing code. I love understanding how entire systems fit together, and I'm hoping to turn years of self-learning, side projects, and curiosity into my first opportunity in the industry.