543 karma · joined March 18, 2016
When I attended college at 43 I was the top student in all my CS classes. Same, when I attended an immersive 3-month bootcamp 5 years later. Now, nearly 10 years later I am an owner in a startup.
I will admit that I had some advantages. First, I was a life-long programmer hobbyist. Mainly a dabbler but I made stuff, mostly games. Second, as a Ux designer, I worked in the industry and side-by-side with developers so I knew my way around the shop. And last, I've been a learner my entire life so getting in the groove to return to school was easy.
Good luck.
What do we make? CADless vertical CAD software (web app) for the construction industry.
When I arrived, some groups in the organization had begun to refactor these Matlab interfaces into WPF applications with slick new updates to the widgets, but it was really lipstick on a pig. After listening to all the stakeholders and users our proposal was to develop a skeuomorphic radio interface (green box with a bunch of dials and frequency display). Only the critical controls were featured on the radio face. All of the configuration options were buried. Now, I get all the eye-rolling when it comes to skeuomorphism as a fad, but it really resonated with our target audience and their superiors. This "Virtual Radio" soon became the defacto style for all communication devices throughout the organization. Because of the animation capabilities of VPF we were able to mimic both the look and feel of the various analog radio controls. It was super realistic. More importantly it allowed us to more easily communicate our designs to a broad audience, including: soldiers, contractors, technicians, and top brass. It has been nearly a decade since I left the company. I hope that this design has gone away. Not because it was ineffective (or trendy), but rather these communication systems needed to evolve to be self-configuring and self-operating, requiring little if any interaction by a soldier other than monitoring. After all, the best interface is one that doesn't need to exist.
But I wasn't happy in Javascript. It wasn't because I was stuck in my OOP brain. I didn't fight it. It just took a long time to embrace declarative programming. In 2018 I attended a bootcamp (Dev Mountain) and learned a single stack that, while opinionated, didn't bring me any fulfillment as a programmer. Mainly for the reasons you described. Too many choices. Not enough opinion. Too much flavor (fatigue) of the month. But mainly, I don't have a lot of joy like I felt when I was doing Ruby.
Fast forward to 2022. My company (a small 3 man development team) has been working on a greenfield project for three years. A massively complex project for such a small team, but finally we are done. Yay. But boy has the journey been wild in terms of our stack evolution. The thought of building a side project in the JS stack I am comfortable with just doesn't sound fun. I long for the warm fuzzies of Ruby. This has almost inspired me to build my passion side-project in Rails to get my mojo back. Thank you.
For anyone that is interested, my current stack is React (Tailwind CSS)/GraphQL (Apollo and Postgraphile)/Express/PostgreSQL with docker CI/CD and AWS lambdas.