3 ms·

I've always been skeptical of the celebrity engineering managers/software entrepreneurs like Graham, DHH, Atwood, Spolsky [1], etc. Just because you made and m

I've always been skeptical of the celebrity engineering managers/software entrepreneurs like Graham, DHH, Atwood, Spolsky [1], etc. Just because you made and marketed one or even two successful products doesn't mean you have any useful generalizable advice. Today people who made something with AI think they have something profound to say about their experience but they don't. All the projects I do now have a significant amount of input from AI assistants but I am going to post "Show HN: my heart rate variability biofeedback webapp" and not add "... that i vibe coded" because the latter one codes me as yet another NPC. (e.g. if I am more successful as AI-assisted developer than some people it is not because I know anything about AI-assisted development which is interesting or generalizable, but it is because of the toolbox I've been using in a lifetime of software development!) [1] Carmack is a true genius who is the exception that proves the rule

iggori 9mo ago
I’m not trying to present myself as a guru or a celebrity engineer. My background is in product and technical leadership, not in being the “hero coder.” I didn’t build an AI system — I built a real production platform where AI was one of the tools in the workflow. The article isn’t meant to be profound. It’s just a practical report from someone who pushed AI‑assisted development into a full product environment and saw where it helped and where it broke. I shared it because some of these patterns might be useful to others, and because I’m also interested in learning from people who’ve taken different approaches. If your experience is different, I’d genuinely like to compare notes — that’s the whole point of posting it here.