Back to the blog
6 min readAICraft
What AI actually changes about software work
Not the end of code. A shift: less typing, more judgment, and new pressure on review.
Code is no longer the bottleneck
Writing a function stopped being the expensive part. The expensive part is deciding which function to write, where it belongs, and what you agree not to build.
Three concrete shifts
- Review becomes the real work. Generating 300 lines takes ten seconds; understanding them still takes twenty minutes.
- Context becomes an asset. Teams that write down decisions get better assisted output than teams that do not.
- Juniors no longer learn by typing. Learning has to be rebuilt around critical reading.
How I apply it
On LingRise I use models for low-ambiguity work: migrations, tests, UI translations. I keep the data model and anything touching billing. The rule is simple: I do not merge what I could not debug at 3am.