The first rule of being in a hole is to stop digging. Ken shows how to use architectures to identify the areas of your code using problematic function
Pro Tip: Start with Directory Structure and add some Human to it.
Adding a bit of human knowledge to the automatically built Directory Structure architecture can improve its visual appeal and utility quite a bit.
Assessing Possible Changes in Source Code (a.k.a. My boss asked me to change this code)
Estimating the impact of changing a function in the open-source covid source code.
A visual tour of cyclomatic complexity
A visual tour of how maintenance risk increases with cyclomatic complexity
Functional Decomposition Architectures FTW
A functional decomposition architecture is easy to make and can help you organize key information about your project.
Analyzing the Imperial College COVID simulation model source code
I used Understand’s CodeCheck feature to examine an influential COVID infection simulation program from Imperial College in the UK as it existed in March 2020 when it was being used to advise world leaders.
Making big graphs manageable with “relationship” graphs
Use”Relationship” graphs, which draw sub-graphs between entities, to break big graphs into little graphs and work your way thru them – turning a big thorny graph into a few easy-to-follow graphs.
Analyzing Boost on Linux, a remarkable story to learn.
A walkthrough on how to analyze a complex open-source project, the Boost library
Finding #pragma directives – A guide to writing your first Codecheck
Your boss tasks you with figuring out how tied your C++ code base is to the ‘#pragma’ compiler directives. Learn to do it quickly with CodeCheck.
Not a software company? SciTools can help you become one.
This article covers easy-to-implement strategies for small to mid-cap companies that operate in industries (Commercial, B2B, and Consumer products) where: software development remains a small part of the expenditures, & maintaining or gaining market share will require more software investments.