blog | sven kanoldt

The best guard for your architecture is probably already in your CI. You just use it for licenses. Architecture rules erode, whether people or agents write the code. With agents it's faster: the rule sits in the docs, the docs fall out of the context window, and the next shortcut compiles just fine. Let's make it stop compiling.

When publishing, having tests, coverage data, code formatting and builds are good practice to have, so that your package looks nice and shiny and is robust for change and contributions. Here we explore how such things can be easily achieved for a dart package.