|
|
|
|
|
by ramon156
128 days ago
|
|
Has OP been at a company where sales people do this? I have, and I can tell you they have not gotten far. There was one PM at my ex-job that showed a dashboard for... well... i honestly didnt understand. I think it was some uptime checks. It broke during his presentation. There's a company I hired at that "built an ERP in 5 days and is shipping the product in June". Same thing happened, it broke when presenting. Basic feature suggestions just returned a "Yes, we can do that!" (they meant they can tell Claude to do it, not that the product could do it). Maybe at some point non-engineers can prompt build, but for now I'd say we're pretty safe. I think engineers give themselves too little credit. Being able to read code is an amazing tool that can only be sharpened through skill. Lastly, I think I commented this ~2 years ago as well. If your product is vibe-codable and is replacing customers, it's a shit product. Similarly, if you can outsource your product on fiverr, its's a shit product. |
|
- making a markdown file with all specs, details and plans - asking claude to search online and suggest some approaches
is a better alternative to doing the research yourself.