sloc VS code-maat

With long functions normally there comes large files as well. People tend to put everything into one file if they also put a lot into one function. So in theory we could take the lines of code as a measurement as well. There are a lot of utility packages out there that solve this problem. One of these tools is called sloc. It will output the number of lines of code within a file. But do not use it directly. The tool I mentioned before includes this by default.

The title of the stackexchange discussion is a little misleading. It really is: '"Hello, World" in what sloc thinks is zero lines of source code'

Most of the top solutions seem to take advantage of bugs in the way sloc tries to parse commented lines. e.g. many are ////

And I'm surprised I don't see a related bug issue in the git repo: https://github.com/flosse/sloc/issues

Still this is a fun read. I'm curious to see what other tricks are out there.

Get a copy of "Your code as a crime scene", then check out two GitHub repos

https://github.com/adamtornhill/code-maat

https://github.com/smontanari/code-forensics

He also wrote Your Code as a Crime Scene and authored the open source tool, Code Maat. I've found both extremely useful in my current job where I took over a code base with immense technical debt.

https://github.com/adamtornhill/code-maat

It's not as neat as that unfortunately. You use this to extract different data from the version control history: https://github.com/adamtornhill/code-maat

Then visualize it however. I have some d3 scripts that came with the book that I've modified and you can track down somewhere on github I'm pretty sure. I mostly use those for demoing it to devs unfamiliar with the techniques though, since it looks cool and is immediately obvious what it's for.

For serious use I dump it into sqlite and use a mix of different scripts and techniques to figure it out. It's been kind of a language playground for me over the years so is in a lot of different languages and is "learning code" in most of them. Cleaning them up and sharing is one of those "maybe some day" things though.

After searching a bit more, it seems like https://github.com/adamtornhill/code-maat is a great tool

The tool code-complexity is closely coupled to JavaScript and TypeScript-based codebases. For other languages like Java, C#, Python, or PHP there are other tools, but one tool that is generic and works for most of the codebases is code-maat. It is a tool created by the author of the book mentioned in the chapter before.

https://github.com/adamtornhill/code-maat#Usage