agentic engineering scorecard→agentic engineering scorecard→practice - custom linting rules that inject in-repo documentation as context→video - harness engineering from OpenAI - 2026-04→what does it mean to do a good job?

what does it mean to do a good job?

Backlinks

stomping code slop

Engineers care about non-functional requirements because they are essentially the distillation of what it means for an engineer to what does it mean to do a good job?. Engineers spend years learning how to build systems that are flexible, maintainable, reliable, that your teammates can build with you. That sort of system... that sort of code accrues leverage over time.

see in context

It is critically important to avoid code slop. One way of doing that is force agents to do a good job. But what does it mean to do a good job?. Experienced engineers know what it means. They've been thinking about it for years and have essentially encoded it into their systems as non-functional requirements

see in context
video - harness engineering from OpenAI - 2026-04

At 8:00 there's a meta epistemological question around what does it mean to do a good job?. We spend years as software engineers learning how to make a code that is flexible, maintainable, reliable, that your teammates can build on top of. The code accrues leverage over time.

Software engineers have a lot of understanding of what the non-functional requirements of a successful systems look like.

see in context