HNHacker News
TopNewBestAskShowJobs

nadis

643 karma · joined April 22, 2016

submissionscomments
nadis··on Build Faster Feedback Loops Using Qualitative User Research
I haven’t tried them yet. Someone I know also founded The Insights Company, which seems to be in a similar space.

For now, I still think it’s valuable to be as close to the research as possible. When I’m in the conversation, I can notice a pause, a reaction, or a facial expression and ask a follow-up right then. I’m wary of handing that part of discovery to AI, especially when it still struggles to understand and tease out what people actually mean. I’d rather keep building that skill myself for now. I also think the effort of sourcing discovery conversations can be beneficial in terms of learning about / finding your best channels.

That said, if the alternative is not talking to customers at all, I’d imagine one of these tools is probably better than nothing.

nadis··on Build Faster Feedback Loops Using Qualitative User Research
Thanks for the kind words and feedback! Cool that you're building in this space as well.
nadis··on Thank u, next: Replacing Next.js with a vibe-coded framework
This is super neat, and not something I'd thought of attempting yet. Thanks for sharing the results, and the thoughtful and well-caveated take on the future of frameworks.
nadis··on YC startups are abandoning .com
Lest we forget, the PG essay: https://paulgraham.com/name.html
nadis··on The Future Is for Everyone – The Path to a Positive AI Future
> Invention, not automation, will be the greatest contribution of superintelligence. Early AI could answer questions and do routine work. Soon it will increasingly help discover new knowledge -- ranging from discovering new drugs to cure a family member's disease to finding new ways to improve your business. While the number of questions a person can ask in a day is limited, the number of valuable things superintelligence can invent to help achieve your goals is unlimited.

Sort of a half-baked tangent of a thought but is it really possible for an AI superintelligence to "invent"?

nadis··on How do we stop vibe coding?
I'd agree with you then! I don't think that case was clearly laid out (or at least I didn't understand your argument to be as such). I'd also say that humans are historically quite bad at communicating intent (even if it comes more naturally and is communicated in natural-language), so I think tools that support human <> agent interaction and iteration are important.
nadis··on Bringing MCP 2026-07-28 to Claude
> "Claude now lists over 950 MCP servers in the connectors directory, used by millions of people every day. This year we shipped support for new protocol extensions alongside features that make MCP easier to build on and deploy"

Where are all these MCP servers? I feel like if I explore the directory, I see the same subset over and over.

Separately, would love to see more love from Anthropic for MCPB. I think this is an exciting and underutilized variation and have been enjoying building MCPB servers.

nadis··on How Do We Stop Vibe Coding?
This piece is more thoughtful than the title initially led me to believe. However, I feel like it's sort of like advocating for us all being able to read/write binary (using a bit of an extreme to prove a point). While there might certainly be benefits to understanding less abstract layers, I don't think it's necessary or even necessarily helpful. That said, I don't think the answer is "turn your brain off completely" but I think that there should be tools that facilitate thoughtful ways of vibe coding with natural language, which is basically another abstraction layer from writing the code and tests yourself.
nadis··on The World-Building Doors Are Open, Again
> "The models are finally ready. Costs of inference are getting optimized with open models, and even on-device models. And, when I first experienced OpenClaw earlier this year, I had the epiphany that it isn’t the models that matter, but the harnesses, loops, and context which will lead to so many new opportunities ahead. Just as we’re learning in enterprise, we can finally invent new products that allow users to do things more naturally, using simple language to express their needs."

This part resonated a lot, personally.

nadis··on AI should earn its keep: Introducing the AI Productivity Guarantee
Seems like a wild move from the Devin team. Very curious about the metrics going into their "estimator" and also that they compared it to human estimates as a measure of success.
nadis··on We tore down our no-code site and went back to code
This is a bit of a tangent but can you explain the Western gaming studios analogy a bit further? It's not something I'm familiar with but am curious (I get the idea and broad parallel, but actually would love to better understand the details).
nadis··on We tore down our no-code site and went back to code
I wondered about this as well, but could also imagine AI tools (perhaps at the application layer and not root-LLM layer) helping to mitigate this - that's a world I've been exploring.

Don't think we're there yet, but it feels like there's a future dream of everyone being able to build and maintain custom software with AI, and not having to make the tradeoff of creativity vs. components that's historically been true with low/no code.

That said, where we are today, completely agree with what you're saying. LLMs like to generate code, and in my experience are pretty bad at iterating on or maintaining the prolific code they've created.

nadis··on The Two X's Problem: Why AI-designed brands feel like AI-designed brands
I found this exploration super interesting, especially the points around when it's okay for design to feel "generic" (when speed matters above all else) versus when design needs to feel "good" (squishy word, but in this case more thoughtful, unique, and deliberate).
nadis··on The Building Block Economy
> The most effective way to build software and get massive adoption is no longer high quality mainline apps but via building blocks that enable and encourage others to build quantity over quality.

I read the first sentence and immediately got excited. Building blocks, but not in the traditional sense of no / low code where you trade off creative flexibility for constrained preexisting blocks. Instead, it's building blocks that enable more people to build higher quality application experiences. Not slop, not copy/paste components, but something creative.

nadis··on Safeguarding cryptocurrency by disclosing quantum vulnerabilities responsibly
> "Quantum computers promise to solve otherwise impossible problems, including examples in chemistry, drug discovery, and energy. However, large-scale cryptographically relevant quantum computers (CRQCs) will also be able to break current, widely used public-key cryptography that protects things like people’s confidential information. Governments and others, including Google, have been preparing for this security challenge for many years. With continued scientific and technological progress, CRQCs are getting closer to reality, requiring a transition to PQC, which is why we recently introduced our 2029 migration timeline."

Is this as wild a news as I think it is? I'm surprised I haven't yet seen more reactions to the 2029 migration timeline plan (proposed?).

nadis··on The Malleable Software That Never Was
> "The real promise of this era is not that everyone shapes and customizes their own tools with malleable systems. It is that agents become capable enough that we no longer need to."

I thought the conclusion here was super interesting, and personally have mixed feelings. On the one hand, love the vision of high-quality tools being available near-instantly in this new AI-native software era.

On the other, I think there's a loss in turning everyone from builders into consumers. Yes, not every person wants to build every tool all the time. But I also think there's something inherently so empowering and delightful in making it possible - albeit not necessary - to build something you've imagined.

We play with legos not because we can't get pre-made toy houses or cars or such, we do it because it's delightful in its own right.

nadis··on Anish Moonka on X: Project Hail Mary is Anti-Slop – details on the tech
> "Then there's Rocky. He's the alien co-lead, and he's not CGI. Neal Scanlan, the creature designer who built the Porgs for Star Wars, spent a full year on this character. Over 300 designs before they landed on the final look. Rocky is a thin, hollow shell, 3D-printed from a digital sculpture, then hand-painted in see-through layers so light passes through him like skin. His arms pop off and swap out depending on the scene: one set has a closed fist for walking, another has tiny motorized fingers strong enough to pick up objects. Five puppeteers (nicknamed the "Rockyteers") operated him in every scene. James Ortiz, an award-winning puppet designer from New York theater, voiced Rocky and controlled him on set. When Scanlan met him, he told Ortiz, "You're Frank Oz, and I'm making Yoda for you." Every reaction Gosling gives to the alien is to something physically in front of him."

The level of detail and puppets / tech / etc. is so impressive.

nadis··on What I Learned Launching CodeYam CLI and Memory on Show HN and Product Hunt
It was quite surprising!
nadis··on The Sourdough Framework
As someone who just recently got into baking sourdough and was literally discussing earlier today some of the challenges around different starters, conditions, and lots of bad / misleading advice online, this is fun to see.

As a bit of an aside, I've found my starter is a lot more resilient than the internet would have me believe. I managed to bring it back to life from the brink after accidentally pouring boiling water directly on it. Fingers crossed no more near-death experiences for it again!

I also find King Arthur's guides and recipes super helpful; recently, I've started popping them into ChatGPT and requesting modifications (e.g. volume, ingredient alterations based on my learnings or needs, altitude adjustments etc.).

nadis··on AI Agent Broke into McKinsey's Internal Chatbot and Accessed Records
If you refresh are you still seeing it? I just got a 404 but am now able to access on refresh.

Copy/pasting below for easier reading in case you still have issues:

An AI Agent Broke Into McKinsey’s Internal Chatbot and Accessed Millions of Records in Just 2 HoursA red-team experiment found an AI agent could autonomously exploit a vulnerability in McKinsey’s internal chatbot platform, exposing millions of conversations before the issue was patched.

A security startup said their autonomous AI agent was able to break into McKinsey’s internal generative-AI platform in roughly two hours, gaining access to tens of millions of chatbot conversations and hundreds of thousands of files tied to corporate consulting work.

Researchers at red-team security firm CodeWall targeted McKinsey as part of a controlled test designed to simulate how modern hackers might use AI agents to probe corporate infrastructure. The experiment ultimately allowed the system to obtain full read-and-write access to the company’s AI chatbot database, according to a report by The Register.

CodeWall’s AI agent identified a vulnerability in Lilli, McKinsey’s proprietary generative-AI platform introduced in 2023 and now widely used across the firm. The chatbot has become a central tool inside the consulting giant. About 72 percent of McKinsey’s employees—more than 40,000 people—use Lilli, generating over 500,000 prompts every month, according to The Register.

Within two hours of launching the automated test, the researchers said their AI agent had accessed 46.5 million chatbot messages covering topics such as corporate strategy, mergers and acquisitions, and client engagements. The system also exposed 728,000 files containing confidential client data, 57,000 user accounts, and 95 system prompts that govern how the chatbot behaves, The Register reported.

Because the vulnerability allowed both reading and writing data, an attacker could theoretically manipulate the chatbot’s internal prompts, quietly altering how it responds to consultants across the company. That means someone exploiting the flaw could potentially poison the advice generated by the system without deploying new code or triggering standard security alerts.

“No deployment needed. No code change,” the researchers wrote in their blog post. “Just a single UPDATE statement wrapped in a single HTTP call.”

How the AI Agent Broke In

The attack began when CodeWall’s AI agent identified publicly exposed API documentation tied to Lilli. The documentation included 22 endpoints that required no authentication, one of which logged user search queries.

While analyzing the system, the agent discovered a classic flaw: The software was taking information from users and plugging it directly into its internal database without checking it first—known as SQL injection. That’s like a building security desk automatically letting anyone make their own keycards to get in.

CodeWall disclosed the vulnerability chain to McKinsey on March 1. By the following day, the consulting firm had patched the exposed endpoints, taken the development environment offline, and restricted access to the API documentation, The Register reported.

“Our investigation, supported by a leading third-party forensics firm, identified no evidence that client data or client confidential information were accessed by this researcher or any other unauthorized third party,” a McKinsey spokesperson told The Register. “McKinsey’s cybersecurity systems are robust, and we have no higher priority than the protection of client data and information we have been entrusted with.”

The Autonomous Cybersecurity Threat

For CodeWall’s CEO, Paul Price, the bigger concern is not this specific vulnerability but the speed and autonomy of the attack itself. The AI agent that conducted the probe operated without human guidance, Price said.

“We used a specific AI research agent to autonomously select the target,” he told The Register. “Hackers will be using the same technology and strategies to attack indiscriminately.”

That shift could enable cybercriminals to conduct machine-speed intrusions, automating reconnaissance, vulnerability discovery, and exploitation at a scale traditional attackers couldn’t achieve. And as companies increasingly deploy internal AI systems like McKinsey’s Lilli, those platforms may become some of the most valuable, and vulnerable, targets.

nadis··on AI Agent Broke into McKinsey's Internal Chatbot and Accessed Records
oh thanks! I'd searched the article related titles and didn't find this; appreciate you sharing.
nadis··on I Left Anthropic: A note and a letter to former colleagues
Why not both? (but also, yes agreed)
nadis··on I Left Anthropic: A note and a letter to former colleagues
Super interesting take...is this something you've seen / experienced before?

I had sort of assumed best intent but probably good to be a little more skeptical / critical but also narcissism or psychopathy seems like a pretty significant deal if true.

nadis··on How to start learning Web Development from scratch?
I think how one might've learned even a couple years ago vs. how one might learn now are somewhat different.

For me, and I consider myself still learning / non-expert, having projects I wanted to build combined with looking for ways to learn the fundamentals (mostly free online courses + books) and then leveraging AI to get unblocked and coached has helped. Of course, take AI answers with a grain of salt.

Harvard's CS50 MOOC is a good "learn how to think about programming" that quickfire introduces you to a lot of fundamentals and challenges.

If you want more structure and more courses, Frontend Masters has a ton of learning paths that are great as well.

I've also heard good things about the Odin project but have not personally tried it out.

nadis··on Show HN: We got tired of managing Claude.md files, so we built something better
> "not just "does this file exist" but "does it still match the actual codebase.""

Completely agree that this is central, and I think thinking about this as a CI problem makes a lot of sense.

nadis··on Show HN: We got tired of managing Claude.md files, so we built something better
Memory management is one of the most challenging parts of working with Claude Code; too little effort or too much, and you waste tokens and Claude gets confused.

> "We attempted to use CLAUDE.md and continue to do so. Our root-level CLAUDE.md helps communicate some of the rules of our repo, such as approaching changes via test-driven development (TDD), as well as tribal knowledge our team has internalized. However, we don’t want to overload it with information about every area of the codebase, given context window constraints and our desire to avoid confusing Claude with irrelevant details."

Having issues with Claude [dot] md seems to be a common experience, and leveraging rules and having a background agent analyze each session is a clever approach here that works well. I've found this to be incredibly helpful.

nadis··on AI should help us produce better code
> "I like to think about shipping better code in terms of technical debt. We take on technical debt as the result of trade-offs: doing things "the right way" would take too long, so we work within the time constraints we are under and cross our fingers that our project will survive long enough to pay down the debt later on.

The best mitigation for technical debt is to avoid taking it on in the first place."

This is actually something I've been thinking about a lot, to the point that I'm now building agentic experiences to try to help make it easier to create and maintain better code and iterate in an AI-centric way while building software.

> "Embrace the compound engineering loop"

Agreed! I feel like making it easier for AI agents to create high-quality code that's easy to test, iterate on, and maintain (without adding tech debt) is crucial here.

nadis··on Meta acquires Moltbook
Just read this other article on the same topic (Axios is paywalled for me): https://www.techbuzz.ai/articles/meta-acquires-moltbook-ai-a...

Interesting times!

nadis··on Ask HN: What Are You Working On? (March 2026)
Thinking a lot lately about how AI is changing software development, and what the ideal development experience might actually look like in the future.

I’m working on CodeYam. We just recently released a lightweight CLI and a feature called CodeYam Memory. The immediate motivation was that when using Claude Code, the AI would repeat the same mistakes and our claude.md files would get stale too quickly to manually maintain. The existing options, including Anthropic’s built-in memory features, didn’t really solve the memory challenge sufficiently for us.

CodeYam Memory runs a background agent that reviews coding session transcripts, looks for patterns of confusion, and generates targeted rules with proper scoping.

It’s a small first step toward the longer-term idea I'm exploring: what an AI-native development experience should actually look like. For now, it’s packaged as a lightweight CLI you can use anywhere you’re running Claude Code.

How to try it:

Install: npm install -g @codeyam/codeyam-cli@latest

Then, from your project root run: codeyam

This will launch a dashboard with further instructions for initializing CodeYam Memory.

Free, runs locally, no login required, and language agnostic. Would love feedback.

More context:

Background blog post: https://open.substack.com/pub/codeyam/p/introducing-the-code...

90 sec demo on our own repo: https://youtu.be/oJ2gTb-lxbE

Demo teaching Claude a real OSS repo (Plane): https://youtu.be/CjOKBwBCcOs

Website: https://codeyam.com/

nadis··on Show HN: CodeYam Memory – comprehensive memory management for Claude Code
Thanks! I don't have insight into what the Claude team has on their roadmap, but given their recent "memory" release I would hope that we see more from them soon. That said, I think this is still quite valuable and helpful to some extent regardless of what they've built and/or build.

Regarding Claude Memory as it exists now (which we use also), from our experience and what we've seen from Claude, it's a much more casual and black box experience.

We needed something more aggressive at extracting out anything complex or confusing to ensure that future sessions had better information and we wanted complete visibility into what memories were being created so we could fix them if they weren't great and ensure that they weren't impacting the context window too much so we built out a rather robust dashboard experience to handle that.

Page 1 of 8Next →