News for hackers. Stuff that matters.

ryan_rudd

Re:How much do your EC2 nodes cost? on Thursday January 29, 2026 @08:10PM (#46819352)
Mine personally costs $30/mo I Use the medium instances.
Re:How are you handling tiny website change requests? on Thursday January 29, 2026 @08:09PM (#46819349)
I keep running into the same thing across different teams and it’s starting to bug me. Non-technical people leave feedback like: “move this up” “this looks weird on mobile” “can you tweak the spacing” “this copy feels off” And then that feedback ends up: half in Slack half in email a screenshot with an arrow or someone just describing it from memory Nothing breaks, but it’s annoying. Engineers have to guess context, ask follow-ups, recheck the page, and small changes somehow take longer than they should. I don’t know if this is just the teams I’ve seen or if this is universal. I’m messing around with a Chrome-based thing that lets people leave feedback directly on the site instead of explaining it in words. Mostly just to see if it actually reduces back-and-forth or if it’s a solution looking for a problem. Before I go any further with it: Is this actually painful for you? Or do you already have a clean way of handling this? If anyone wants to try it when it’s usable, I’ll give a free month in exchange for honest feedback. Not trying to sell anything here — genuinely deciding whether this is worth continuing. Curious how others deal with this.
Hi HN, I’m Ryan, a student and solo dev. I built PushPilot because I was tired of the "context-switching tax". Whenever a client or PM finds a UI bug—like a misaligned button or the wrong hex code—they usually send a screenshot. I have to stop my deep work, find the file in my repo, fix the CSS, and open a PR. It’s a lot of friction for such a small change.

What it actually does: It bridges the gap between the browser and your source code. You click the element on the live site, tweak it in a mini-inspector, and PushPilot opens a Pull Request in your GitHub repo with the code fix already written.

About the Safety & Permissions: I know giving a new tool GitHub access is a big ask. I've focused on keeping it as safe as possible:

Scoped Permissions: It only asks for access to the specific repos you choose.

No Auto-Merge: It only opens a PR. It never touches your main branch directly. You still have to review and hit "Merge" yourself.

Transparent Code: The PR shows you exactly what lines were changed so there are no surprises.

Why it’s cheap right now: I literally just put this live, and I want it to be a tool that freelancers can just "grab and go". I’m charging $9/mo for the solo plan because I’d rather have 100 people using it and giving me feedback than 5 big companies paying more. Since my run costs are extremely low, I don't feel the need to charge a premium while I'm still learning.

It currently works best with React and Tailwind, as that's my own stack. I’d love for you to try it out and tell me if the workflow makes sense or if I’m over-engineering a simple problem.

Why it’s cheap right now: Honestly, I just deployed this, and I want it to be something that a freelancer can just "grab and go." I’m charging $9/mo for the solo plan because I'd rather have 100 users using it and giving me feedback than 5 large companies using it and paying more. My run costs are super low, so I don’t need to charge a premium while I’m still learning.

Show HN: I built a tool that turns browser clicks into GitHub PRs for CSS fixes

https://getpushpilot.com/

Hi HN, I’m Ryan, a student and solo dev.I built PushPilot because I was tired of the "context-switching tax". Whenever a client or PM finds a UI bug—like a misaligned button or the wrong hex code—they usually send a screenshot. I have to stop my deep work, find the file in my repo, fix the CSS, and open a PR. It’s a lot of friction for such a small change.What it actually does: It bridges the...

( Read More... | no comments | on HN )

How do you map runtime text back to source code without source maps?

I’m building a dev tool that tries to do "reverse rendering"—you click an element on the frontend, and it opens the source code that generated it in your IDE.I’ve got the easy stuff working perfectly. If the DOM says <p>Hello World</p> and the code contains return <p>Hello World</p>, my AST chunker + vector embeddings find it instantly.But I’m hitting a wall with dynamic...

( Read More... | no comments | on HN )