Codacy, a code quality tooling company, writes about static analysis, code review, Scala, Kubernetes, and PostgreSQL.
HN commenters link it for its cyclomatic complexity explainer and Scala learning guide; no one offers much opinion on the blog itself.
It seems that typed actor support it somewhat incomplete. Once you wanted to use typed actors with routers and resizing, there was no documentation. There were some mailing lists posts with suggestions that don't work. I don't know if anything changed in the meanwhile, but this blog post suggests that it's still not well-supported:
http://blog.codacy.com/2014/01/29/typed-actors-with-routing/
One thing that I dislike about the Akka implementation of actors is that they can't block, because this would block a thread in the thread pool. Quasar's implementation of actors allow you to block on e.g. I/O, because Quasar can preempt fibers that are parked. This makes Quasar's actor framework much more powerful and more Erlang-like.
Specifics depend on project(s)/work environment(s); but literate programming[0] and using/enforcing coding/git/versioning standards can help automate a lot of things[1][2][3].
aka re: outdated responses -- blog and/or email list for when 'new/updated version' pushed out with errata/change log location.
[0] : https://blog.bitsrc.io/literate-programming-a-radical-approach-to-writing-code-with-documentation-ebb5dc892cd7
[1] : https://blog.codacy.com/coding-standards
[2] : https://github.com/git-lfs/git-lfs/blob/main/.github/workflows/ci.yml#L15
[3] : https://github.com/git-lfs/git-lfs/blob/main/.github/workflows/ci.yml#L15
Code complexity is a thing. It doesnt describe understandability but its a pretty decent proxy in my experience.
> In 1976, Thomas McCabe Snr proposed a metric for calculating code complexity, called Cyclomatic Complexity.
https://blog.codacy.com/an-in-depth-explanation-of-code-complexity/
There is also likely some simple metrics you could get by looking at names of things alone.
Common substrings, length, and diversity of names are probably decent indicators.
take a look at: http://blog.codacy.com/2015/07/03/how-to-learn-scala/