Nathan Yergler interviewed at Velocity 2012
summary
Technical debt gets defined as anything that increases the cognitive overhead of working with code, shifting the conversation away from blame to concrete friction. There is caution about the instinct to rewrite because rewrites rarely succeed without evidence, so the recommended approach is incremental, evolutionary changes. Ignoring debt hands control to inertia—entropy will creep in—but business tradeoffs matter: sometimes imperfect legacy code still generates revenue, so engineers must quantify problems and communicate costs and options upward.
AI-written summary · about
