ebenes's comments

On: What I learned building an opinionated and minimal coding agent

[ebenes]

I second that from using Pi for two weeks now. It's not a little but a massive difference. My estimation is about 5-10x longer lasting token windows. Getting done more is just one of the benefits. I've briefly summarised my experience in this article: https://ewaldbenes.com/en/blog/the-only-coding-agent-you-ll-...

On: What I learned building an opinionated and minimal coding agent

[ebenes]

I cannot recommend Pi enough: https://github.com/badlogic/pi-mono/tree/main/packages/codin...

I'm working with it for about 2 weeks now and absolutely love it. I can't think of going back to Claude Code CLI, Codex or similar tools.

Here's my experience in a nutshell: https://ewaldbenes.com/en/blog/the-only-coding-agent-you-ll-...

On: My personal reasons to not run my Nginx reverse-proxy inside Docker

[ebenes]

* Docker containers can be modified at runtime, it is just more involved to do so. Hot-reloading inside Docker works best if you mount a host directory.

It drives the container philosophy to an ad absurdum. When I serve paying customers then I refrain from what is possible. I try to stick to what appears to be the simplest thing.

* I haven't encountered a corrupted Nginx binary, so far. I think that it is very unlikely to happen. I consider my Nginx binary "almost immutable" even without Docker. Since I am the only one working on my VPS I also know who to blame if that's not the case :D

I see Docker as an amazing fit for isolating business applications. They tend to have many dependencies (often less stable than evergreen libraries like libc), get continuously update and deployed.

On: My personal reasons to not run my Nginx reverse-proxy inside Docker

[ebenes]

I'm no expert in hardening for server security like SELinux.

As far as my understanding goes containers per se are no security mechanism. Rootless containers are as good as rootless processes with chroot.

So this comment resonates with my understanding.

My feeling is that containers give you more possibilities to introduce security holes if you aren't diligent.

On: My personal reasons to not run my Nginx reverse-proxy inside Docker

[ebenes]

The section about the "Docker as an additional dependency" didn't transmit the message correctly which I tried to convey.

It is about:

Everything that something depends on makes it a little more likely to introduce failures which I want to minimize if reasonably possible.

I corrected the section.

On: How to Kill a 35 GB SQLite Database: Rethinking Pagination Without Offset

[ebenes]

Tweet author here:

Apparently the poster wants to provide the context what circumstances lead to the problem and further down how to solve it.