Small-Company Frontend Developer: AI Didn't Announce My Exit, It Raised Everyone's Benchmark by One Level
A frontend developer at a small company shares his core reflections from six months of AI coding practice: what is truly uncomfortable is not that AI can write code, but that it raises everyone's output expectations by one level while pushing the judgment calls AI cannot make and the errors AI makes back onto the same individual. He offers three coping principles and lists four categories of tasks he firmly refuses to delegate to AI.
A frontend developer with eight years of experience at a small company, where there is no dedicated frontend team; he handles all three platforms, build processes, deployments, and midnight alerts single-handedly. Over the past six months, he has delegated every task possible to AI, sharing a practical observation: what truly makes me uncomfortable is not its ability to write code, but that the benchmark has been changed.
This observation is more specific than the common anxiety about replacement. Previously, he delivered one page per week, which the boss considered normal; now, colleagues using AI produce three proposals in a day, and the boss asks him why he is so slow. AI did not announce anyone's exit; it simply raised everyone's expectations by one level and left each person to chase that increment. The most difficult aspect for small companies lies in this: having to make judgments AI cannot perform while also patching up the parts AI gets wrong, leaving not a single hour of the day fully dedicated to thinking.
He drew a clear line. Tasks where AI is indeed effective share a common trait: they have standard answers. Regular expressions and various legacy compatibility codes, which previously took half an hour to research and ten attempts to test, can now be verified and used in two minutes; for a ten-year-old table page requiring Excel export last quarter, AI wrote the entire xlsx segment directly, and after adjusting two style points, it went live; pasting compressed error stacks allows for rough localization, saving half the search time; writing comments, documentation, and technical solution explanations for the boss are where the most time is saved.