Posts connected by the documentation tag.
3 posts
Engineering quality is a property of what ships. Quality engineering is the practice that produces it, and that practice cannot be handed to another team. Quality, security, and documentation belong to the engineer who builds the thing, and the reward system has to pay for those behaviors or they quietly stop.
Six months of building AI infrastructure and coaching coworkers on their agent workflows taught me the bottleneck is no longer code creation. Someone can write ten thousand lines in a day, but nobody found a way to make a colleague understand those ten thousand lines any faster than in 2019. Validation is still the vehicle through which humans actually learn a system, and that work has not been automated.
Why the word 'hunting' matters: context doesn't just lie around waiting to be picked up. Real context requires active investigation, tracing code, chasing state transitions, and turning what you found into something the whole team can use.