Hmmm I got bad eyes that makes me hate consolas, looks like a good contender to operator mono, will give this one a shot.

Jesus christ the graphs are even borderline hilarious

It's starting to grow a life of its own, slowly and slowly starting to become self-aware.

I've just read the wikipedia page about her, that's halfway awesome and fucking crazy.

There are bunch of them, really.

But for general structure, using your end-user's user experience path (from start to end) as a guide and avoiding buzzwords as much as you can usually help. Think of Stripe's documentation, you want something as easily digestible as that.

- Software Design Patterns: https://en.wikipedia.org/wiki/Software_design_pattern

- Azure Application Architecture Guide: https://docs.microsoft.com/en-us/azure/architecture/guide/

- Azure Cloud Design Patterns: https://docs.microsoft.com/en-us/azure/architecture/patterns...

- Azure Architecture Framework: https://docs.microsoft.com/en-us/azure/architecture/framewor...

- Azure Cloud Adoption Framework: https://docs.microsoft.com/en-us/azure/cloud-adoption-framew...

- Cloud Computing Patterns: https://www.cloudcomputingpatterns.org/

- Microservice Architecture Patterns: https://microservices.io/patterns/index.html

- Amazon's Builders Library: https://aws.amazon.com/builders-library/

Apache Kafka's documentation is pretty good, too: https://kafka.apache.org/0102/documentation.html

Also, for a 10,000 foot overview of popular open-source tools, see https://aosabook.org

The sign-up requirement is a big onboarding hiccup.

Like yo, I don't even know what it really does yet, why are you asking me to create an account? Do you really expect your users to capture your value prop based on just screenshots alone?

Thanks for that feedback. I'm working on that, I'll let users be able to play around with editing the demo with no save functionality without creating an account.

Jesus christ this opt-in landing page is helluva waste of bytes.

Amazing inputs.

I'd also suggest a top-down approach where you start with a flexible end goal you'd want to achieve (e.g. be a full-stack dev), in which case you can start by babystepping a hands-on approach (e.g. learning javascript, learning client-side and server-side of things). Complimentary fundamental course outlines can also help, e.g. Comptia A+ gives you hardware fundamentals, Comptia Network+ gives you networking fundamentals, CloudAcademy can get you started on working with cloud providers like Azure/GCP/AWS, and so on and so forth.

It's easy to get lost in the theoretical side of things, being able to test them out in action as soon as you can could give you quite an ideal balance.

It's not crucial per se, but more like one of the lowest hanging fruit out there in getting someone to go out of their way and socialize.

Totes this. I got no degrees too fam but the way I approached it was to do side gigs in making websites for small businesses while making small github contributions.

Higher-paying gigs want some bit of track record and those small websites and github stuff are the lowest hanging fruits for me imo.