We develop one or more apps that we deploy on-prem. An app for us is a git repo with a docker compose file. On-prem is either a Linux server or a Linux vm that we have ssh access to (normally via Wireguard vpn).
For app updates, we use ansible to ssh into machines, run pre-deployment scripts, pull git repo and docker images, restart containers and run post-deployment scripts.
It could be better, but it works for us.
The biggest bottleneck we have now is communication with customers, scheduling of updates, letting them know of breaking changes or new features, that kind of stuff.
The apps are provided "fully managed". They dont know and don't care about the details I just described, but they do need assurances that everything is done "properly".
What we think would help us a lot is a way to easily let them know of new releases of any apps they have installed, let them read release notes, docs, and be able to either deploy on-demand or schedule a deployment at a certain time.
Although having fewer things for us to do is nice, what is crucial is to oversee deployments and make sure they are successful (and intervene if not).
More like giving formula for free to new mothers to begin with, and when they wouldn't produce their own (as there was no "demand") they would later need to buy more formula.
There was a stackoverflow question (IIRC) long ago on how to disable a mobile phone's camera shutter sound, and the answer was to record the sound, inverse it and play it when the camera is activated so that the two sounds cancel each other out. Not sure if it worked though, or if it helps in your case, as precise timing is needed for this to work.
Hey man, I don't know you and you don't know me, but if I may I'd like to point out that you don't have to explain your feelings or thoughts to a bunch of strangers on the Internet. Just getting them out there, in this form, is a gift for anyone willing to receive it.
The last few years I've been working on a fairly big django project written by someone learning the problem domain and python/django at the same time.
I have a lot of similar stories and I you are absolutely right to encourage people to learn the basics, at least (looking at you, indexes and perf tools).
We're talking about having our cpu hitting 80-90% and rising internal temperature to 70-80C, while executing a task thats normally performed tens or hundreds of times during the workday.
A couple of carefully planned indexes, a bit of sql shuffling, is all it takes sometimes.
The upside of working with cheap bare metal servers is that you catch these things early on (5 concurrent users and your server is toasted). Fun times.
I know that the whole "it doesn't work without javascript" story sounds like "get off my lawn", but content authors, esp on HN, need to realise that quite a few of us refuse to browse the Web with JS enabled esp on mobile devices.
With JS the experience on the mobile web is garbage. It's difficult enough to find quality content as it is, we don't need all the added "benefits" of JS.