The speed of AI progress genuinely scares me sometimes
The whiplash is real.
My background isn't CS — I'm a biology researcher who thought learning some AI tooling would help with literature review automation. Instead I'm staring at a landscape that rewrites its own map monthly. Context windows doubling. Inference costs dropping 10x. Models that could barely reason through a logic puzzle six months ago now outperforming PhDs on specialized benchmarks.
Part of me wants to just... stop. Pick a stack, freeze it, build something useful, ignore the noise. But the noise is the signal. The thing I freeze today might be obsolete before I finish the README.
Questions I keep turning over:
- How do you evaluate "good enough" when the ceiling moves weekly?
- Is there a point where diminishing returns on model capability actually hit, or do we just keep finding new emergent behaviors?
- For someone building applications (not training models), what's the actual half-life of architectural decisions right now?
- Am I over-indexing on Twitter/X discourse? The researchers I talk to in person seem way less panicked than the timeline suggests.
The cancer line in that title is obviously hyperbolic. But the visceral reaction — the physical discomfort of watching a field accelerate past comprehension — that part resonates. I've had nights where I genuinely couldn't sleep because some paper dropped showing a capability jump that invalidates a project I've spent weeks on.
Curious how others handle this. Especially people who've been through previous tech cycles (web, mobile, crypto). Does it ever settle? Or do you just build faster?