Click any tag below to further narrow down your results
Links
Elliot Morris argues that prototypes used to force engineers to communicate clearly, surface real problems, prove competence, and engage with reality, but LLM-built prototypes break most of those benefits. He thinks the useful future prototype is a sharp, single-thesis experiment rather than a big, sprawling demo.
- Prototypes once delivered four bundled benefits: clear communication, early problem discovery, a visible competence signal, and forced contact with reality. LLM prototypes keep only the first of these reliably.
- LLM output tends to drift toward a generic "average" answer, so the builder can end up communicating something they didn't intend without noticing.
- Experienced engineers make rougher, smaller prototypes because they test one narrow thesis. Morris suggests the key question is now "what specifically does this prove, and why should I care?"
Felix Rieseberg, a hiring manager at Anthropic, argues that AI has made the traditional coding interview obsolete and that engineers without seniority can now move fast by building working prototypes. He offers a playbook for newcomers to get noticed by tying their work to business impact.
- Anthropic stopped giving coding interviews because Claude now outperforms candidates on small coding challenges, and top builders succeed regardless of how they do on them.
- Newcomers have an advantage in spotting friction and questioning assumptions that old-timers stop noticing, but they usually lack the status to get ideas funded.
- AI has cut the cost of execution, so a junior engineer can build a focused prototype over a weekend and skip the usual PRD and buy-in process. Keep it to one good idea, aimed at a business goal.