non-functional requirements
non-functional requirements

Backlinks

experienced engineers can codify many non-functional requirements

^ link not trackeds can codify many non-functional requirements

see in context
practice - using vibe coded slop for prototyping

... where that iteration is actually part of the SDLC building block -- design phase. It's complicated. I suspect at the end it would get handed off to a developer who would then shape it to adhere to the non-functional requirements. Seems like a neat process, honestly.

see in context
stomping code slop

The problem with link not tracked is that it violates all sorts of non-functional requirements.

see in context
video - Github researcher on how we should collaborate with agents in teams - 2026-04

This will allow the review phase to be more limited. Perhaps it can then go back to being more of an engineering-focused activity where engineers work with agents to ensure that the non-functional requirements are supported by the code.

see in context