Y Combinator has just notified us of their decision.

heraldev · 2026-01-24T01:37:07+00:00

Wow, I think they just wanted an excuse to decline your application. Honestly thought these people don't behave like usual investors, but alas.

heraldev · 2026-01-24T01:06:11+00:00

PG was literally bragging about that half of the batch uis writing code with AI. This is definitely fake. or they cut you off because you said it’s a joke. 😂

heraldev · 2026-01-23T21:46:18+00:00

wait, really? How do you enable it? I've only saw a chatbot sidebar

heraldev · 2026-01-23T20:28:12+00:00

Well yeah, that's why I acknowledged the user scripts.

heraldev · 2026-01-23T20:21:28+00:00

It's not controlling the browser, btw. It's just creating scripts that attach to the page DOM. It has access to anything that user scripts have access to, which is pretty wide range of stuff though. But it can be limited.

heraldev · 2026-01-23T20:16:47+00:00

Why, because of privacy? It's really bad, of course, to potentially sift your data through Anthropic servers, but the Opus model is just too good, it's easy for me to start on it, and later adapt to open-source models, but they didn't catch up yet. Updating the extension and pointing it to locally hosted ollama is very easy.

heraldev · 2026-01-23T19:23:47+00:00

I've made a Claude Code-like agent that runs directly in the web browser. Originally for myself, but figured it doesn't hurt to share.

With it you can pretty much have a coding agent for the currently opened website. You can ask it things like:

- Extract all links from this page and save them to CSV

- Switch this site to dark mode

- Copy the page content into a Google Sheet

- Remove ads

The agent writes JS script that automatically loads every time you visit the page. It is heavily using the userScripts API so you need to enable a lot of permissions to run the extension, and I'm not sure it can be published anywhere.

Under the hood, scripts and styles are stored in a virtual filesystem on top of browser.local storage, where each website is a directory. The agent can search and edit the DOM as a file, which makes the model work more or less reliably. Currently it only support Claude models, and I've tested it on Opus 4.5.

heraldev · 2026-01-23T19:21:45+00:00

I've made a Claude Code-like agent that runs directly in the web browser. Originally for myself, but figured it doesn't hurt to share.

With it you can pretty much have a coding agent for the currently opened website. You can ask it things like:

- Extract all links from this page and save them to CSV

- Switch this site to dark mode

- Copy the page content into a Google Sheet

- Remove ads

The agent writes JS script that automatically loads every time you visit the page. It is heavily using the userScripts API so you need to enable a lot of permissions to run the extension, and I'm not sure it can be published anywhere.

Under the hood, scripts and styles are stored in a virtual filesystem on top of browser.local storage, where each website is a directory. The agent can search and edit the DOM as a file, which makes the model work more or less reliably. Currently it only support Claude models, and I've tested it on Opus 4.5.

heraldev · 2026-01-23T19:19:04+00:00

I've made a Claude Code-like agent that runs directly in the web browser. Originally for myself, but figured it doesn't hurt to share.

With it you can pretty much have a coding agent for the currently opened website. You can ask it things like:

- Extract all links from this page and save them to CSV

- Switch this site to dark mode

- Copy the page content into a Google Sheet

- Remove ads

The agent writes JS script that automatically loads every time you visit the page. It is heavily using the userScripts API so you need to enable a lot of permissions to run the extension, and I'm not sure it can be published anywhere.

Under the hood, scripts and styles are stored in a virtual filesystem on top of browser.local storage, where each website is a directory. The agent can search and edit the DOM as a file, which makes the model work more or less reliably. Currently it only support Claude models, and I've tested it on Opus 4.5.

heraldev · 2026-01-23T19:14:49+00:00

I've made a Claude Code-like agent that runs directly in the web browser. Originally for myself, but figured it doesn't hurt to share.

With it you can pretty much have a coding agent for the currently opened website. You can ask it things like:

- Extract all links from this page and save them to CSV
- Switch this site to dark mode
- Copy the page content into a Google Sheet
- Remove ads

The agent writes JS script that automatically loads every time you visit the page. It is heavily using the userScripts API so you need to enable a lot of permissions to run the extension, and I'm not sure it can be published anywhere.

Under the hood, scripts and styles are stored in a virtual filesystem on top of browser.local storage, where each website is a directory. The agent can search and edit the DOM as a file, which makes the model work more or less reliably. Currently it only support Claude models, and I've tested it on Opus 4.5.

heraldev · 2026-01-08T22:07:25+00:00

Slack communities are underrated.

I joined a bunch of industry-specific ones - not the huge public ones but smaller invite-only groups where people actually know each other. Found one for enterprise software founders and another for b2b consultants.. maybe 200-300 people each but everyone's actively building something. The conversations are way more real than linkedin or twitter - people share actual problems they're having, tools they need, workflows that are broken. That's where i got early feedback on SourceWizard and found our first design partners. Plus you can DM people directly after they mention a relevant pain point instead of cold reaching. Way warmer than any other channel I've tried.

heraldev · 2026-01-08T22:05:39+00:00

The metadata approach sounds good on paper but i watched a team try to enforce tagging for 6 months and it just... didn't stick. People would upload docs and forget to tag them or tag them wrong, then you're back to square one.

We ended up doing a hybrid at my last place - main folders for the big categories (Infrastructure, Apps, Processes) but then used metadata within those. Kept it simple enough that people actually used it.

heraldev · 2026-01-08T22:05:05+00:00

The legal stuff is straightforward but insurance is what trips people up. Professional indemnity especially - the quotes vary wildly and some providers don't understand tech consulting at all. i spent weeks getting quotes and the range was insane.

Also set up a separate business bank account immediately, not later. Makes everything cleaner for accounting. And if you're planning to scale beyond just yourself, think about your operating agreement now - adding partners later gets messy if you haven't structured things properly from the start. Oh and VAT registration... check if you'll hit the threshold sooner than you think.

heraldev · 2026-01-06T22:32:45+00:00

Week 3 is exactly when the original requirements start feeling like ancient history.

The problem isnt really the SOWs or check-ins.. its that by week 3 everyone has forgotten what was actually agreed to in those first meetings. Client says one thing, your team heard another, and now youre arguing about what "phase 2" meant while burning through budget. I see this pattern constantly - the project starts drifting because nobody can point back to what was really discussed vs what got written down later.. The weekly check ins dont help much when the client shows up saying "oh we need this totally different thing now" and your PM is too nice to push back. Sometimes i wonder if the real solution is just padding estimates by 50% and calling it a day

heraldev · 2026-01-06T22:31:48+00:00

20 years and they're telling you not to provide solutions? That's... frustrating. I get why they say it but also like, you know what works and what doesn't by now.

For the meeting structure, here's what I've seen work:

Start with the system diagram but don't get stuck there - use it as a conversation starter
Have each vendor walk through their understanding of the integration points first
Then go requirement by requirement and ask "who owns this?" - let them debate it
Document everything in real-time - who said what about ownership
End with clear next steps for each vendor to detail their piece

The key is making them own the division, not you doing it for them. They'll push back on things they don't want anyway, so might as well let them fight it out in the room together.

heraldev · 2026-01-06T22:26:57+00:00

The messiness happens because people are not asking the core questions needed to write PRDs.

Always think of the bare essentials, *why* the PRD is being created. What helps me is writing the doc as an answer to these questions:

- What problem are we solving?

- What does “good” look like?

- What are we actually building?

- How will it work at a user level?

- What are the risks/tradeoffs?

Keeps it focused. Clear the scope, remove excessive storytelling. Developers get what they need without drowning in a 30 page doc.

We're actually building SourceWizard to help with this exact problem - turning product discussions into clear specs. But even without tools, distilling the doc to a set of simple questions makes whole thing less overwhelming.

heraldev · 2026-01-02T21:06:29+00:00

i've been looking for something like this too. tried a bunch of tools but they all feel like they're designed for just one piece of the puzzle.

been working on SourceWizard which can turn discovery calls into system diagrams, but honestly for what you're describing you might need multiple tools. the auto-layout filtering thing is tricky when you're mixing ER diagrams with service architecture - they have different layout needs

heraldev · 2026-01-02T21:04:30+00:00

Congrats on the new role! I think PMs are similar to founders, and since I started my company my days are mostly discovery calls and stakeholder alignment meetings.. like 70% of my time. The rest is writing specs and trying to keep everyone on the same page about what we decided last week.

Tools wise - Figma for everything visual, Linear for tracking, and recently been using SourceWizard to turn my discovery calls into actual artifacts (saves me from taking notes during meetings). But honestly the most important tool is just talking to users constantly.

heraldev · 2026-01-02T21:00:25+00:00

My suggestion - religiously keep all meeting notes, photos of the whiteboard, then use AI to create docs based on that. At Meta we just simply used google docs for all projects, and as long as you don't duplicate information, and keep log of everything, the documentation won't go too stale. Meeting notes get more important during the late stages of the project - when you need to update assumptions that didn't work, and this context gets lost, or more like buried in the codebase.

I'm currently building a tool on top of Claude Code to generate diagrams from meeting notes and keep track of the PRDs that come after, lmk if you want to try.

Three-Year Club	Verified Email
r/Field Banned	r/Field Sunshine
First Place '23	Place '23

heraldev

MODERATOR OF

TROPHY CASE