dorianniemiec

What would you think of easier-to-debug infrastructure building blocks? I'm building an easier-to-debug web server and reverse proxy, and I want to know how this would compare to trying to use AI SRE agent to reduce debugging friction. Or maybe both complement each other?

Or it could be just better instrumentation...

I don't even have experience with Terraform at all...

I'm using something different myself: a Docker Compose + reverse proxy config + some other support files, pushed to a private GitHub repo, which then triggers a GitHub Actions workflow that leads to the repository being pulled on the VPS and the infrastructure to be "rebuilt" (docker compose up, reverse proxy graceful restart).

I wanted to use this post as a source to write on my web server project's blog on why debuggable web infrastructure matters even if AI SRE agents exists, but the idea got delayed and I ended up posting it on HN... :')

I thought of MariaDB, maybe MongoDB, maybe even flat-file DBs on very old comment systems, but not Google Sheets... :)

Even though I'm starting to hand-code more in my project, I think AI can still be useful for example for finding security vulnerabilities. Although I think too many are vibe-coding projects for no one...

A simple 404 Not Found posted on Hacker News? :)

Yeah, I saw this "open-slopware" list listing many battle-tested web servers as "permissive AI policy", while one of the alternatives (not all though, some inherit battle-testing) isn't really battle-tested. In fact, I saw entangled codebase and not-so-good coding practices.

Yeah, the (poisoned) AGENTS.md file reads lots like "f*ck AI", which feels like anti-AI dogmatism for me. If I really wanted to use this project, I would use Coreboot instead or fork it to remove proprietary blobs.

So what would many anti-AI people say, now that critical infrastructure (Linux, OpenSSL, systemd, MariaDB, and so on) is AI-assisted?