/Matthieu Cneude

Measuring Software Complexity: What Metrics to Use? tl;dr: Complexity metrics are flawed but, can be "useful to isolate a part of your codebase which might be more prone to defect." Matthieu believes it's a combination of metrics, experience, and experiments that reveal complexity in a codebase. He explains and uses the following metrics in this order when analyzing complexity: (1) LOC. (2) Code shape. (3) Structural coupling (common and content coupling). (4) Logical coupling.

featured in #272


A Vim Guide For Experts tl;dr: "This is the sixth part of this series to learn Vim from the ground up."

featured in #251


A Vim Guide For Intermediate Users tl;dr: (1) Ways you can organize open files using buffers, windows, tabs, and the argument list. (2) Useful motions to jump quickly from one place to another in your entire codebase. (3) Mapping new keystrokes to old keystrokes or commands, and more.

featured in #219


Burnout in Software Development Demystified tl;dr: A guide to burnout - causes, symptoms, how to talk about it to your manager and strategies to counter it. "Strong social bounds are the best medicine against chronic stress."

featured in #171