luodaint

4 ms·

1. 31.▲
   Tell HN: Calculated the price for Canny at 1k/5k/50k users–see how it adds up

   1 points by luodaint 5mo ago|0 comments
2. 32.▲
   by luodaint 5mo ago

   The paper hits the nail right on the head, but it misses the mark on the next constraint: how to decide what to build. In the old days when writing code took up a lot of resources, the constraint was self-correcting since being off in your
3. 33.▲
   by luodaint 5mo ago

   That's right, and even more alarming: no one is pushing back, not only the engineers. The leadership team has AI estimates. The product team has AI estimates. Even the engineering team has AI estimates. Everybody says "Ship."
4. 34.▲
   by luodaint 5mo ago

   #10 needs more emphasis than it receives. Cheaper code doesn't automatically lead to good product decisions. Instead of focusing on whether you can build it, the scarcer resource becomes whether you should build it. And most teams lack
5. 35.▲
   by luodaint 5mo ago

   I have deployed a fully-fledged B2B SaaS product with authentication, multi-tenancy, real-time webhooks, three languages internationalization, all through Claude Code's loop. Skill atrophy is not an issue since I am not in competition
6. 36.▲
   by luodaint 5mo ago

   The trap isn't agentic coding, it's using it as fancy autocomplete. When you delegate whole tasks with real acceptance criteria, not just single functions, the economics change completely.