My biggest takeaway was to have my core database tables (user, subscription, etc) backed up every 10 minutes, and the rest every hour, and test their restoration. (When I shut down the site it was 1.2TB.) Having a script to quickly provision a new node—in case I ever needed it—would have something up within 8 minutes from hitting enter.
When I compare this to the startups I’ve consulted for, who choose k8s because it’s what Google uses yet they only push out 1000s of database queries per day with a handful of background jobs and still try to optimize burn, I shake my head.
I’d do it again. Like many of us I don’t have the need for higher-complexity setups. When I did need to scale, I just added more vCPUs and RAM.
I could share a python script that is working pretty reliably for me.
I'm sure it's all my poor prompting and context, but it really seems like Claude has lost 30 iq points last few weeks.
The current stack I'm using is Django/Python, HTMX, Alpine.js, and TailwindCSS. Yes I know the middle two use Javascript under the hood, there is no way around that for client interactivity. But they do support the HATEOAS principal (https://en.wikipedia.org/wiki/HATEOAS) which has been a breath of fresh air imo. The book "Hypermedia Systems" is also a great way to achieve the mental reset needed to abandon modern web frameworks and go back to things that actually work, in terms of web development.
It's basically creating a "get paid to spam the internet with anything" system.
https://www.nytimes.com/2024/07/31/well/eat/ultraprocessed-f...
They key isn't how you say it, the key is that you consistently do it so that people learn that when you say it, you mean it.
As far as how to do it confidently? The same way you say "that is a tree" when you're looking at a tree. You're 100% sure you don't know, just say it. The rest is probably in your head. That's been my experience at least.