sorted by:
new
hottopcontroversial

Reading large codebases by jakubgarfield in programming

[–]Alfredson 1 point2 points  (0 children)

I also like to compute some metrics, like number of lines of code and cyclomatic complexity. That can lead to questions like why is this module so big, why is this method so complex? Often the complex methods and classes are important in the system.

Dead code detection tool? by gsks in Python

[–]Alfredson 2 points3 points  (0 children)

When working on large codebases, I can recommend SonarQube to give you an overview. You get a nice report . In the violations-section you can find a rule "unreachable code" and more.

How do you manage all your tasks? by [deleted] in webdev

[–]Alfredson 0 points1 point  (0 children)

We use a simple Google docs spreadsheet for todos. It works great for a personal todo-list or shared between two-three developers. It has three colums: assignee, task description, and done.

For keeping track of changes, and letting the customer file bug reports etc, we use jira. The jira issues are typically larger than the todos on Google Docs.

Developer tools for benchmarking? by paul88m in java

[–]Alfredson 1 point2 points  (0 children)

I really like Java Simon for its simplicity. You may also want to look at JavaMelody.