Hacker Newsnew | past | comments | ask | show | jobs | submit | dack's commentslogin

yeah there's way more demand, and at the same time, it's way easier for the company to build and maintain (with the help of AI). Great to see!

if you include "it turns out that", you're implying that maybe you thought the same as them in the past, but looked into it, and learned something interesting. if you omit that, you're just correcting them and subtly implying that they aren't as smart as you (e.g. it was obvious to you)

i don't know what else they can say about their own business.. but it's clearly cope.

sure, there's a lot of compliance/legal concerns, but AI is probably already better at reading all the relevant information and encoding that into a system than humans.

I don't think a non-technical person is going to one-shot it, but a technical person could today. The biggest issue would be marketing and maintenance (companies aren't going to buy from a single random person who might abandon the project at a moment's notice)


last i checked, you can't annotate inline with planning mode. you have to type a lot to explain precisely what needs to change, and then it re-presents you with a plan (which may or may not have changed something else).

i like the idea of having an actual document because you could actually compare the before and after versions if you wanted to confirm things changed as intended when you gave feedback


'Giving precise feedback on a plan' is literally annotating the plan.

It comes back to you with an update for verification.

You ask it to 'write the plan' as matter of good practice.

What the author is describing is conventional usage of claude code.


A plan is just a file you can edit and then tell CC to check your annotations

they have pretty fierce competition though, so i doubt this is intentional. my guess is they just have a million things to do and that isn't at the top of the list


if i were you @susam, i'd use claude code to parse all these submissions into your json file! i bet opus 4.5 would do it flawlessly


what are your goals? it's usually tough to sell things to developers because they are very particular about how they want their software to work, and also would rather build their own tools much of the time (which is increasingly true with AI now).

if you really want to sell it, you should probably make sure that you have customers willing to pay, which means talking to potential customers and getting them on a waitlist. i think it's usually more likely that other people don't care about your software like you do (because you built it to be exactly what you want and know how it works) and even then, aren't willing to pay to use it (or pay very much)

if you're not very concerned about making money and mostly just want something nice for yourself that other people _might_ care about, then sure, go for it! i build software like that all the time


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/


I didn't like that there was a long delay after you move your mouse, and since all the calculation happens on the frontend, i figured you could easily make it ~instantly update and follow you around. So i (well, claude) made a version that does that and i think it's more fun. here's the code you can paste into the console at pointerpointer.com: https://pastebin.com/f7YqQNxg


this is pretty cool, it seems they reuse every image by translating it a little when your cursor is within a range


yeah it's crazy to think that claude 4 has only been out a month. And the previous iteration 3.7 was launched only in February!

but also I think the interesting thing is that people didn't jump on MCP immediately after it launched - it seemed to go almost unnoticed until February. Very unusual for AI tech - I guess it took time for servers to get built, clients to support the protocol, and for the protocol itself to go through a few revisions before people really understood the value.


yeah current AIs are surprisingly good at figuring out which tools to call and how to call them!


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: