willisrocks

Or you can get the best of both worlds--use frontier models to build a spec/plan, and use cheap models (open source or not) for implementation. Your max or team plan can go a lot further this way without giving up much for quality. Play with something like Superpowers to make this really approachable.

I can't speak for the other books, but The Pragmatic Programmer is one of my favorites.

I had previously looked into Cloudflare's on-demand offering and was also disappointed that their service seems out of reach for bootstrapped or early stage startups.

As a heavy reader, for fun and for work, I need to be able to track what I've read just to be able to figure out the name of the author of those books I really liked a couple of years ago. The one feature that I've yet to find in something like Goodreads is notifications of when new books from an author you like are coming out. For me, that would be a killer feature.

You're already doing one of the mains things I do for self-learning: checking this site every morning. I bookmark interesting stuff for later and try to play with the things that really catch my eye. Either way, keeping an eye on what other people are talking about is important.

I tend to do well with watching videos as a way to get familiar with new tools, stacks, languages, concepts, etc. Then I need to get my hands dirty. For my first few years learning programming, I went pretty deep on personal projects.

Additionally, I've always had an interest in the ops side too, so I got comfortable with stuff like Docker and Linux pretty early on. Having a general sense of how your software gets built and deployed really helps, in my opinion.

The biggest thing for me was building up the confidence that I would be able to figure out whatever was thrown my way. Between my self-learning and internships, I stepped into my first job after school with enough confidence to really hit the ground running. That mindset continues to be an asset now.

My CS program was heavy with theory, so it was important for me practice building software the whole time. This is probably the biggest reason to avoid juggling the degree and a full-time job in my mind. Your coursework will keep you plenty busy on its own, let alone doing your own personal learning and projects!

Regardless of the approach you take, I wish you the best on your journey! I love talking about this stuff, so I'm always happy to share my experience.

I was in a similar situation as you. I completed a BA in Econ then ended up working in tech. I wanted to move into a full-time development role, so I made the decision to go back to school full-time for my BS in CompSci.

I'm happy that I made the decision that I did, but I had already been pretty heavy into self-learning for years before going back to school. I could see both approaches working, but I felt more comfortable getting my foot in the door as a developer with the degree.

Working full-time while working towards your CompSci degree sounds rough! I didn't even try it.

Not sure how helpful that is for you, but I wish you the best of luck.