Hacker News Reader

Full thread

coder4life

Run it through a pretty printer?

Try for no warnings with your static code analyzer / linter / compiler?

Make tests for it

Add logging

Put it on gitlab pipeline, make a CI/CD for it

Make it as a standalone docker container (see above point)

Update or make the readme.md

View on HN

I second tackling all analyzer/linter/compiler warnings, but add them to CI and do the test coverage first.

This will allow you to surface metrics (for advocating the cause to management) and make cleaning up the code an ongoing task for technical-debt sprints.

Reply on news.ycombinator.com