I started with the basics by reading a few books like Clean Code, Clean Architecture, etc. I also started reading protocol specifications. For example, I read

I started with the basics by reading a few books like Clean Code, Clean Architecture, etc. I also started reading protocol specifications. For example, I read the XMPP protocol as I was setting up ejabbered. At work I try to find inefficiencies and opportunities in the way we do things across all domains. When I find an issue, I create a quick draft of the problem and potential solution, along with the pros/cons etc. I share that with the broader architectural group leaders and end up demo'ing it in front of them. So far, I've been able to get maybe a dozen such ideas implemented (best part - I didn't do the actual work but get to see the benefits like faster builds, or when I did some things for our mobile app UI an easier way to work with dynamic components, etc.). On the side I am trying to build up a company since last summer in the AI space. I'm still trying to figure out what exactly I want to build, talking to people/customers, but along the way I'm building a ton of the underlying foundation for the business. I've learned a lot about writing extensible and modular code, and across languages and technologies. It is a lot of fun, and I doubt I'd have learned all that on my own at my job.