{"id":1812,"date":"2024-10-09T09:53:00","date_gmt":"2024-10-09T16:53:00","guid":{"rendered":"http:\/\/10kdev.net\/?p=1812"},"modified":"2025-07-17T10:20:33","modified_gmt":"2025-07-17T17:20:33","slug":"a-plan-for-quality","status":"publish","type":"post","link":"http:\/\/10kdev.net\/?p=1812","title":{"rendered":"A Plan for Quality"},"content":{"rendered":"\n

Here’s a plan for team code quality I’ve devised over a several years of working with different applications. Most of these can be done open source.<\/p>\n\n\n\n

Each category represents a type of monitoring methodology. This is by no means comprehensive, but is a good guide for the type of project hygiene that has to be done to maintain a good running application.<\/p>\n\n\n\n

INPUTS<\/h1>\n\n\n\n

The input bin of this plan involve what things we look at before we decide to act — data and observable collecting.<\/p>\n\n\n\n

Of course any of these tools can be ran in almost any of these stages, but I’ve put them into a best fit bin for matter of brevity.<\/p>\n\n\n\n

Monitored Quality<\/h2>\n\n\n\n

Monitored quality looks at the aspects of the running applications and infrastructure; pretty much runtime state. A lot of devops is involved. <\/p>\n\n\n\n

Monitoring of server conditions and application logs, database performance and optimization, specific coverages for OWASP or security breaches. In that monitoring is also running some sort of continuous testing — load type tests (JMeter etc.), performance checks.<\/p>\n\n\n\n

Automated Quality<\/h2>\n\n\n\n

Automated quality we are scanning pre-production code looking for errors.<\/p>\n\n\n\n

At this level we have code quality scanning (SonarQube etc.), dependency scanning (Dependency Track etc.), security scanning (BurpSuite etc.), and UI\/UX scanning (Lighthouse etc.).<\/p>\n\n\n\n

Developer Driven Quality<\/h2>\n\n\n\n

Developer quality involves tools and observations during the development process — usually on local.<\/p>\n\n\n\n

Few developers check their build logs and should (other than runtime)– it’s an endless list of issues. Quality checks before committing — Sonar, linting, AI tools, code coverage — should all be a given. Also, pull requests and code reviews before merging to main branches.<\/p>\n\n\n\n

At a higher level — architectural upgrades (watching framework sites for updates, warning from scans, etc.) and developer experience — tools, build times, local issues — should be constantly revisited.<\/p>\n\n\n\n

OUTPUTS<\/h1>\n\n\n\n

Dashboards<\/h2>\n\n\n\n

Dashboards monitor real time data, especially useful for production support. <\/p>\n\n\n\n

Dashboards can be made for Automated Quality and Developer Quality, but generally I consider those part of engineering management and not production monitoring.<\/p>\n\n\n\n

Ticket Process<\/h2>\n\n\n\n

The ticket process involves a triage — to see if the ticket should even be logged.<\/p>\n\n\n\n

The inputs come from all three areas, and can product a ton of backlog — sometimes it’s best just to focus on blockers, criticals and majors.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n","protected":false},"excerpt":{"rendered":"

Here’s a plan for team code quality I’ve devised over a several years of working with different applications. Most of these can be done open source. Each category represents a type of monitoring methodology. This is by no means comprehensive, but is a good guide for the type of project hygiene that has to be […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"http:\/\/10kdev.net\/index.php?rest_route=\/wp\/v2\/posts\/1812"}],"collection":[{"href":"http:\/\/10kdev.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/10kdev.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/10kdev.net\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/10kdev.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1812"}],"version-history":[{"count":5,"href":"http:\/\/10kdev.net\/index.php?rest_route=\/wp\/v2\/posts\/1812\/revisions"}],"predecessor-version":[{"id":1825,"href":"http:\/\/10kdev.net\/index.php?rest_route=\/wp\/v2\/posts\/1812\/revisions\/1825"}],"wp:attachment":[{"href":"http:\/\/10kdev.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1812"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/10kdev.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1812"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/10kdev.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1812"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}