Ask HN: What are you working on? (May 2026)
811–820 of 1001 posts
Re: Ask HN: What are you working on? (May 2026)
#812It started with informal among friends things, and we’ve found through our networks there’s a lot of demand beyond her girlfriends wanting high tea etiquette. Now she's diving into tech people who have elevated into higher ranks but don’t have experience yet in fine dining with clients and leaders.
It’s been a lot of fun doing something that has nothing to do with AI and really minimal tech in general. The events have been a lot of fun, really feels like we’re cooking something.
Re: Ask HN: What are you working on? (May 2026)
#813This starts from my frustration when opening large CSV files, but later evolved to a log/data analyzer that loads arbitrary format in constant time (O(1)). https://github.com/Verticalysis/Hitomi The secret: I engineered an incremental combinatorial parser capable of processing customized format from a steam. Any inputs, including file or the stdout from a command, are first chunked and then fed to the pipeline. The U…
Re: Ask HN: What are you working on? (May 2026)
#814Re: Ask HN: What are you working on? (May 2026)
#815Re: Ask HN: What are you working on? (May 2026)
#816Picking a tool and setting up a knowledge base to have technical and design decisions, notes, and maintenance logs in a single place is usually straightforward. It's the consistently feeding the system with high-quality data part that we get stuck at.
Eventually, I have to input information when I lack the necessary mental bandwidth, I end up creating incomplete entries that lack essential details.
The initial idea is to develop a chat interface that allows us to share random pieces of information, either through text or voice, and have it scanned for actionable data that can be ingested. Then it should start probing the user, looking to expand and refine the new information, connecting it with existing data, and general maintenance of the repository. All with no active guidance.
For instance, I could launch it and say: “Today the team and I discussed how frequently the databases for project A and B should be synced. We established the user can tolerate up to 10 minutes of tardiness", at which point I would expect it to:
- Create a note of this discussion happening - Check and fix the existence of entries for projects A and B - Link the note to the projects - Create database entries for both projects - Look for previous entries that could be linked to the projects - Ask for further explanation of how we came to that conclusion
Re: Ask HN: What are you working on? (May 2026)
#817It visualizes React / Next.js codebases as an interactive graph so you can understand how features and components connect without manually tracing files.
Main focus right now is helping with:
PR reviews (understanding blast radius / impact of changes) onboarding to large codebases understanding unfamiliar parts of a system faster
Also experimenting with summaries + security analysis directly on components.
Still early, but it’s been pretty useful for me so far.
Re: Ask HN: What are you working on? (May 2026)
#818Re: Ask HN: What are you working on? (May 2026)
#819Cursor for AI PMs/Forward Deployed PMs.
A lot of engineers are trying to build the “Cursor for PMs.” As an engineer-turned-PM with several YOE in both roles, I appreciate their intent, but most are not solving the elephant in the room for the next generation of PMs, so I decided to step in.
Engineers wrote code. Designers produced design artifacts. Product Managers HAD to write PRDs as a way of communicating intent to gain alignment across teams; it was never their only job (would’ve been easy if it was!). The PRD was the means to the end, not the end itself, which is where most engineers are stuck building another AI-native text editor to become the next Cursor for PMs.
Today’s AI tools can generate PRDs, fancy roadmaps, complex spreadsheets, beautiful decks, and no-context OKRs, but the real job of PMs was always quick alignment, principled decision-making, and leadership buy-in with little to no data, something no AI tools can reliably solve today. We now have a unique opportunity to (potentially) solve these big, hairy problems with AI. I’m starting with orchestrating humans and agents to make better decisions.
Loving it so far. AI tools make me wish there were more hours in a day!