|
|
|
|
|
|
by miki123211
8 days ago
|
|
|
Another approach to this is "build mechanism, not policy" (also of Unix philosophy fame). Encapsulate the hard parts in libraries, ship the topmost layer as codegen templates that depend on those libraries, and let agents / devs modify that topmost layer to their heart's content. This often beats putting everything in libraries and having to expose customization points everywhere. This is the approach taken by the Shadcn UI library (which became popular just as agents entered the scene), but it generalizes far beyond UI. |
|
|
Might be more recognized from the X Window System design principles rather:
> Provide mechanism rather than policy. In particular, place user interface policy in the clients' hands.
https://en.wikipedia.org/wiki/X_Window_System_protocols_and_...
It wasn't part of the original Unix philosophy, but I see that went through several revisions.