Hacker Newsnew | past | comments | ask | show | jobs | submit | unsloppable's commentslogin

You should see how it freaks out over disk corruption caused by a bad kernel patch.

Had to /hug a few times before it got back to work.


There is no stop. Only forward.

Is it time to vibe code my whole stack so I'm secure through obscurity?

Only half joking.


I'm working on barely / barelyvm [0] which replaces docker desktop with a new MacOS app and docker context.

I've been using Theo's "hill climbing" technique [1] applied to more than just UX and getting pretty good results.

The new docker context points at a customised VM with a patched kernel to do memory and storage ballooning.

That is, containers return unused ram back to the Mac and things like volume prunes get trimmed from the disk automatically freeing up disk space.

It also does some magic to decide if a container is "idle" and will auto suspend the container to swap getting more ram back for Mac OS. If all containers get suspended the guest VM itself hibernates to disk and scales down to zero.

On any request to one of the container ports the whole thing comes back in milliseconds and responds like nothing happened.

This is mostly built for those of us with limited ram and storage in our macs but also for those who have memory hungry build steps that happen in your dev container builds but only need a fraction of the ram for running your app.

[0] https://barely.dev [1] https://youtu.be/xq0eB8vxeqk


They didn't ignore it. Their view is that meta's only assets are office chairs.

Very strange view, but sure.

Is the AI in the room with you right now?

The Machine is everywhere. Watching us with ten thousand eyes. Listening with a million ears.

I imagine Sam and Dario would be more likely to take Greer's route than Finch's, what with their ideas of superintelligences as gods.

I've been doing this with one of my VM projects and hit message caps really quickly, threads start stalling out.

In the end I needed to use a coordinator.md file to backdoor messages and locking state in a pull instead of push model to keep them running overnight.

I need a lot of inter-thread comms because my app has to build a kernel inside itself and then replace itself to run tests which meant I was hitting concurrency and load issues with multiple sessions trying to run things like benchmarks against their own work tree.

Will projects hit the same issue?


Most of these were never bad ideas. Big tech has been poorly incentivised for a decade or more. We killed code review before we got copilot.

They dropped the ball so badly with copilot. I would not be surprised they entirely drop the ball on review too.

Pull request review is by and large going away everywhere I talk to. Everywhere else it's a bottleneck they're trying to solve.

GitHub needs to figure out how to position itself as an orchestration layer between team members and their agents before slack eats their lunch.


Thanks for linking this. I've reached a point I need to overhaul one of my MacOS apps and these laws are the perfect find.

What's the best approach to applying these in practice? Should I evaluate every screen with each of these laws in mind or should I evaluate the app entirely one law at a time?


Give and agent the llms.txt and ask it to read.

I have a dedicated agent profile that specifically owns this task and I tell the other agents to only send screenshots to it and ask for feedback.


I gave it to an agent along with the transcript of Theo's recent hill climbing to fix uis video.

Hoping Jev on open router can save me.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: