lobo_tuerto

Joined 18 years ago

Karma
7,470
Submissions
1,493
Member since
Dec 5
Website: https://lobotuerto.com You can reach me at: [email protected]

Fullstack Engineer

PELT stack: Phoenix, Elixir, LiveView and Tailwind CSS. Can do some Vue.js too ;)

Empathic, honorable, humble, smart, honest, thoughtful, with a knack for travel & seeing new places.

===============================

Zen hunting.

===============================

In case you want to look at a CV: https://lobotuerto.com/cv

---

meet.hn/city/20.8052225,-99.8837376/Querétaro

View on Hacker News

Recent submissions

Comment · 7 days ago
The truth is, if they could they would, and they should. But they can't, not yet.
Comment · 16 days ago
Try this:

    npm install -g --allow-scripts=@opencode/cli @opencode/cli
Comment · 1 month ago
Is like in the covid era, where did the money go when all the prices spiked? I bet it's some kind of redistribution.
Comment · 2 months ago
We won't. AI engineering is here to stay whether people like it or not.

See what some guys like Linus Torvalds, or Eric S. Raymond are saying about. It's not so much about "vibes" but using the tool (yes the AI tool) in a certain way that can propel yourself towards your goal at unprecedented speeds.

Comment · 3 months ago
Better than losing all the data created between no backups.
Comment · 3 months ago
Comment · 3 months ago
Comment · 3 months ago
I'm OK with the space being taken. I want total isolation, don't want changes in my main or sandboxes to ripple to one another. As for maintaining, it's only a `rm -rf ~/sandboxes/*` away anyway.
Comment · 3 months ago
That's why I went with a different strategy and scope: Copy the current Git repo into a sandboxes dir, mount that copy in the container. The tradeoff is disk space allocated per sandbox, but I'm OK with that.
Comment · 3 months ago
Just a little bit, I want coding agents to work their own disposable copy of a git repo. Here is a quick rundown of what it does:

It copies the current Git repo into the sandboxes dir, mounts that copy at /workspace in the container. The original repo is never mounted writable, so I don't care if the agent goes to town/wild in there (peace of mind).

It also builds cached Debian/mise/Elixir/Phoenix images, can start a private Postgres container, publishes selected localhost ports, reuses dependency/build caches, and prints commands on exit for reviewing diffs, exporting patches, applying them back to the real repo, or reopening the same sandbox later. Pi, and OpenCode are configured with proper LLM access keys (derived from my own).

So spinning a new sandbox is a matter of cding into a project directory and run something like: `ai-sandbox --port 4000 --postgres somedbname` or `ai-sandbox --port 4001` if I don't need DB support. Then when running the server in the container I can access it from the host machine to review in my browser.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton