For a more baby-steps approach to resiliency, one might start running software on less-virtualized computers, creating a small home-lab, running software on bare-metal hardware that you actually own.
It makes the most sense (to me) for app platforms like Firebase to invest deeply in the AI application development wave. Creating something from scratch with prompts is impressive but the gap between something that works locally to something that people can use is still large enough to require some dev & ops expertise.
Even though the aim here is different, sustainability through repair and reuse is uplifting. It's also a reminder that 10-year-old computers can do a lot and most of us may not need the latest shiny laptops.
I agree with the team-size aspect, but the age argument won't always hold.
Junior folks bring their own energy, flexibility, hunger for learning and the resilience to unclear future. As folks get more mature, growing egos, stability expectations, tendency to settle down can get in the way.
Overall, this boils down to the fact that teams and people are not just head counts and there's a factor of chemistry need to be considered depending on the culture, founders, geography and the business itself.
Thanks for creating this content, this looks pretty good and it was a good time for me to refresh my basics about computer networks.
I tried checking the content with my kindle (a Kindle Touch paperwhite 6 inches) and the first chapter rendered pretty good, with images and text aligning as intended. However the second chapter did not render the first figure and beyond. Chapter 3 rendered OK, similar to Ch 1.
A few more feedback if that helps for enhancing the format even more:
- Colors, and references to those do not work on a kindle. I only saw one minor use of colors (red, green) in Chapter 1 so that's not a blocker.
- For some reason, the kindle browser doesn't put left and right margins on the page, so the text uses the full length of the device.
- Links are rendered with a pale gray, sometimes hard to distinguish.
- Figuring out why the Chapter 2 did not render would definitely help.
Workflowy, alongside a regular email and calendar. Workflowy is very simple yet flexible and has the tools that make me operate without thinking much.
It allows me to quickly keep a GTD-ish list of stuff going on and action items needs to be taken and I can organize them as detailed as needed with labels, colors, etc. I find the simplicity/features ratio work well for me.
AFAIK, PaaS solutions like heroku have a similar way of working, at least for side-projects. Here, you deploy a container and Google runs it somewhere and Heroku containerizes your application every time you push it. Similar to here, Heroku's free hobby containers also go to sleep in ~30min inactivity.