“Guide” is doing a lot of heavy lifting there. There’s an infinity of difference between asking an AI to make something and using an AI to do the scutt work, looking over the code it made, running IRL tests, asking “why X? Why not Y?”, swearing at it like a junior dev, asking it to fix a,b,c then finally getting acceptable code.
And even with all that - when you set it up correctly - it’s still faster than doing it yourself (in certain circumstances).
It feels more like doing project management / “software engineering” than clacking the keys. It’s amazing how different LLMs approach the same task though; I find Codex to be much more by the book than Claude, for example. The Qwen’s are like Labradors - eager to please, clumsy, crash into things a lot. GLM and Kimi are different again. Etc.
You can’t let anything just “make me X, make no mistakes”. By the time you type in a ticket (with GO/NO GO gates, acceptance criteria etc) you might be looking at 500-1000 lines of text (which is why a re-usable template and procedures are important). You need repeatable procedures, acceptance tests - the lot.
And so it goes.
It depends. Some services, like native XMPP, don’t work through a standard HTTPS reverse proxy. Tailscale, NetBird etc. handle them fine, but you need direct TCP access or TCP forwarding instead. Other services can use HTTPS without problems.
I think the HTTP versus HTTPS distinction is less important when you only access services through a trusted LAN or a private tunnel.
Tailscale and NetBird already encrypt traffic between devices, and isolated containers provide another layer of protection. Plain HTTP on a LAN still carries some risk, but I’d argue that HTTPS is less critical in these circumstances.
In your particular case, NetBird’s reverse proxy can handle HTTPS for the browser while the service itself uses HTTP over the encrypted tunnel.
Just make sure that your proxy actually restricts access to your private network.
So the answer is “it depends”.