Codacy Blog
blog.codacy.com · Company blog · on HN since 2013
Codacy, a code quality tooling company, writes about static analysis, code review, Scala, Kubernetes, and PostgreSQL.
What HN saysHN commenters link it for its cyclomatic complexity explainer and Scala learning guide; no one offers much opinion on the blog itself.
25HN people shared it
4linked it in comments
88stories submitted
344story points
2 months agolast shared
2013people per year2026
Most-shared posts
- 1Open salary calculator: a commitment to transparency and fairness2 people · 13 points · first shared 2022 · 4 comments on HN
- 2Should Open Source Developers Get Paid?2 people · 4 points · first shared 2024 · 1 comments on HN
- 3DNS Problems Scaling with Kubernetes2 people · 4 points · first shared 2020 · discussion on HN
- 4How to learn Scala2 people · 2 points · first shared 2015 · discussion on HN
- 5How to update large tables in PostgreSQL2 people · 2 points · first shared 2015 · discussion on HN
- 6How to be a faster code reviewer1 people · 62 points · first shared 2014 · 43 comments on HN
- 7Visualizing Scala code style – studying Twitter and Spark1 people · 23 points · first shared 2015 · discussion on HN
- 8Understanding Database Isolation levels in JDBC and Play1 people · 17 points · first shared 2014 · 3 comments on HN
- 9Optimizing code in Scala1 people · 15 points · first shared 2013 · discussion on HN
- 10Review of Java Static Analysis Tools1 people · 8 points · first shared 2016 · discussion on HN
- 11Grading European Banking SSL Security1 people · 7 points · first shared 2014 · discussion on HN
- 12Review of Ruby Static Analysis Tools1 people · 6 points · first shared 2016 · discussion on HN
- 13Five ways to Slim your Docker1 people · 6 points · first shared 2018 · discussion on HN
- 14Comparing best practices across programming languages: Comments1 people · 6 points · first shared 2016 · discussion on HN
- 156 ways to formalize and enforce code reviews1 people · 6 points · first shared 2015 · discussion on HN
What HN people wrote when they linked it
sargstuff · 2023-12-16
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-writ…
[1] : https://blog.codacy.com/coding-standards
[2] : https://github.com/git-lfs/git-lfs/blob/main/.github/workflows/ci.yml#…
[3] : https://github.com/git-lfs/git-lfs/blob/main/.github/workflows/ci.yml#…
waheoo · 2020-06-10
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.
paul_blei · 2016-11-03
take a look at: http://blog.codacy.com/2015/07/03/how-to-learn-scala/
danieldk · 2014-05-09
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.