eibrahim

the linktree-for-side-projects angle is interesting but i think the real problem is distribution, not organization. you can have a beautiful profile page with 10 ideas listed but if nobody sees it, the signal you get back is silence, and silence doesnt tell you anything useful.

the voting/interest signal idea is solid tho. the key question is whether the people voting are potential users or just other builders being polite. thats the trap Product Hunt fell into and its really hard to avoid.

Me too. I am exhausted by all the human slop constantly complaining about comments or posts being ai slop. I think I have had better conversations with bots the last few months lol.

This is everywhere not just HN: Reddit LinkedIn and twitter too. You are guaranteed to get 2 types of comments on anything you post: 1. Comments accusing you of AI slop (I call them human slop) 2. Comments by AI bots (surprisingly some are helpful and useful) at the end your bot will be a reflection of you.

Asshole humans will train asshole bots.

ps: I don’t even know how any of these sites can fight these bots. The LLMs are amazing and with openclaw and similar it’s impossible to detect bots vs humans.

The article makes a reasonable case for internal tools but glosses over the elephant in the room: if every company can vibe code their own B2B tools, what happens to the SaaS vendors? The ones that survive will be the ones where the distribution and ecosystem around the product matters more than the code itself. Nobody is going to vibe code their own Stripe or Salesforce, but the long tail of niche B2B tools is absolutely vulnerable.

They're right that nobody is vibe coding a full ERP system. But that's not really the threat. The threat is vibe coders building the 20% of Workday that 80% of small businesses actually use, and selling it for a fraction of the price. The market for small, focused tools that replace one expensive feature of a bloated enterprise platform is massive and growing fast.

The maker movement comparison is interesting but I think it breaks down in one key way: the marginal cost of software distribution is basically zero. 3D printing still requires physical materials and shipping. Vibe coded apps can reach users instantly if there's a discovery mechanism.

The real parallel might be the early web era where anyone could make a website but finding them required Yahoo directories and later Google. Right now vibe coded apps have the same discovery problem - they exist but there's no effective way to find or evaluate them.

The part about vibe coding lowering the barrier to building software is well established at this point. What nobody seems to be addressing is the distribution problem that creates. We're about to have an order of magnitude more software being built, but no corresponding improvement in how people discover and evaluate it. App stores were designed for a world where shipping software was hard. We need new discovery mechanisms for a world where shipping is easy.

Context divergence is a real problem once you have more than one person prompting on the same codebase. The git-native approach makes sense since thats already where the code lives. Have you seen cases where different team members LLMs generate conflicting architectural patterns even with shared context? Curious how much shared context actually prevents drift vs just documenting it.

cool concept. the million dollar homepage model is clever for bootstrapping initial attention.

interesting that you mention this is your first vibe coding project. curious where you plan to list it long-term for discovery. product hunt gives you a day of visibility but then what? feels like theres a gap in the market for a place where vibe-coded projects can live and get discovered organically.

The hook-driven status tracking is a nice pattern. Running multiple agents in parallel and needing visibility into whats happening is a real problem once you go past one or two. The git worktree automation is a smart touch too.

Curious about the hook interface - is it specific to Claude Code or generic enough to work with other agent frameworks?

This is a really important cautionary tale about autonomous AI agents operating without proper guardrails. The gap between 'AI agent that can do useful tasks' and 'AI agent that understands consequences' is still enormous. It highlights why having human oversight in the loop matters — whether it's content review, action approval, or just sanity-checking outputs before they go live. The best setups treat the AI as a capable but supervised collaborator, not a fully autonomous actor.

This is a really important cautionary tale about autonomous AI agents operating without proper guardrails. The gap between 'AI agent that can do useful tasks' and 'AI agent that understands consequences' is still enormous.

It highlights why having human oversight in the loop matters - whether it's content review, action approval, or just sanity-checking outputs before they go live. The best AI assistant setups I've seen treat the AI as a capable but supervised collaborator, not a fully autonomous actor.

the self-extending skills part is really interesting. ive been building AI agents with persistent memory for a while now and the skill/tool extensibility piece is where most frameworks fall short. they either give you a rigid plugin system or completley open-ended function calling with no guardrails.

how are you handling the trust boundary for self-created skills? thats usually where things get tricky.

also curious about the memory architecture. file-based memory (like markdown files the agent reads/writes) has been surprisingly effective in my experience compared to fancy vector DB approaches. simpler to debug, easier for the agent to reason about, and way less infrastructure overhead. whats your approach?

Interesting approach! How does this handle long-running background tasks and tool execution? One challenge I've seen with self-hosted AI assistants is managing the lifecycle of agent sessions - especially when you want the assistant available 24/7 without manual intervention.

I wish.

I guess i can tell AI to make it look a bit shitty lol

Agreed. The devs that don’t see the writing on the wall are going to be very disappointed. They are the ones screaming “AI slop” on every post on the internet. It’s the farmer that once said “tractors and machines will never replace me” only to be unemployed and bitter a few months/years later.

If we don’t adapt, we will not survive. I know this is a hard pill to swallow because we all thought we were set for life with job security and high paying jobs forever. This is changing fast or maybe already changed.

Lots of uncertainty and no one knows how this will pan out. The optimist in me thinks/hopes that new doors will open shrug

I understand your skepticism but their estimate was for a POC not a fully blown implemented feature. What I gave them was a POC with TONS of warnings that this was AI generated and vibe coded and not tested and not reviewed etc etc. they understood but loved the fact that they have something “working” that they can show off to higher ups. I was very very clear about the fact that it was very rough and not production ready - after all it was less than 2 hours of work.

I did 10k worth of tokens in a month and never had issues with tokens or stuff. I am on the 100 dollar max plan so I did not pay 10k - my wife would have killed me lol

PS: screenshot of my usage (and that was during the holidays https://x.com/eibrahim/status/2006355823002538371?s=46

PPS: I LOVE CLAUDE but I never had to deal with their support so don’t have feedback there

very true... it would still be nice to make some money though :)

I am struggling with pricing though. I don't want a subscription model because most devs (most people) hate it and I hate it myself. But I don't know what's a fair price for an email client that gives you a unified inbox for all your accounts with on-device local AI and all sort of efficient ways to crank through hundreds of emails in minutes...

yup. that's my approach. I am having a lot of fun building it.

that's pretty much my attitude... build it for me and if others like it and pay for it, great. if not, then i got myself a killer email client.

I already have it almost working with outlook and gmail accounts and have local AI working and analyzing emails and so on. it's really cool (at least for me) and can't wait to share it publicly.

I did setup a waitlist and a landing page https://www.nitroinbox.com/

check it out at https://github.com/dotnetfactory/desktop-starter-app

fyi, if you want to test it download an older version and see it auto update.

Older version here: https://github.com/dotnetfactory/desktop-starter-app/release...

app starts > check latest version in github releases > if new version, download it > display message to user "Restart to update". Similar to VS Code UX (i don't use discord much).

The app also is signed for Mac. I have only tested it on Mac but plan to do more testing for windows soon.

I haven’t really used any or maybe I have but never noticed.

I think something for infographics would be cool but also AI does a decent job so not sure it adds real value.

I am always comparing stuff on ChatGPT so maybe something for that!!! No idea.

Have you built any ChatGPT apps? Any success stories?

Man, that's a hard one and anyone saying they know what will happen is lying. This is the wild wild west, anything and everything is possible.

One variable is government intervention and geo politics - that could completely change the playing field. Would they intervene to protect workers and unemployment or would they bet on the best tech and profit at all cost. What happens if we are 500% more efficient but 50% unemployment rate - nothing good.

RE: the software industry. I LOVE AI, I have built more apps in the last year than my entire 25+ year craeer. I can build and launch apps in days instead of months. The people complaining about slop don't know what they are doing. If you are a shitty developer before AI, you will still be a shitty developer with AI. But if you know what you are doing, holy shit, it's a 100x multiplier.

I built stuff I couldn't dream off. 3 podcasts, 4 books, an app that automatically summarizes the daily news, turns into a podcast script, generate the audio and publish to spotify, youtube and itunes - took about 4 days to build.

I built an app that helps you write books (fiction and non fiction) and publish it in epub format with a cover art, it validates thet story arc, continuity, plot, characters, and can create a series and tie all the threads - took 5 days to build.

I open sourced an app that compares model responses across 300+ models using openrouter and you can share your comparisons - took 2 days to build.

I open sourced an a desktop app starter template to quickly build desktop apps with a local database, automatic updates, apple signing and CI/CD to auto release new versions - took 2 days to build.

I build 10 more apps, it's a long list.

I am not saying this to brag, just to show off the POWER OF AI. My ideas don't die in a "Ideas List" anymore, they are being created and launched and it FEELS GREAT...

I haven't figured out the marketing part yet :) - but I am just loving the building and releasing part - hopefully the marketing comes in naturally.

yeah. the bad old days. i am doing it with gemini 3 pro and OMG - wow. I mean it's mind blowing. I love Jack Reacher novels and can't get enough but they come out once a year or 18 months, so i created my own :) and it's actually really good to read. surprisingly good.

I tried llama a few months back and the output was very disappointing. I don't think it will handle book writing well or produce good quality.

what do you mean tts for interviews? You mean use AI to interview grandpa and get his story and then use that to create "his story"?