Articles by Martin M. Lacey
WHY we need pull request descriptions, and HOW to craft them
Pull Requests (PR) descriptions enable us improve built-in quality and engineering practices, through understand the context of Why the code has changed.
Engineering Practice Feature Flags
Feature Flags Part 1 - How To Keep Trunk-Based Branching Reliable
Are you part of The Solution or part of the Problem
Software Engineering Behavior
Engineering Practice Engineering Interviews
Engineering Interviews – Breaking Barriers with Generative AI
Fishbowl Dev CoP
Experimenting with a New Developer CoP Format: Fishbowl Discussions
Rotting Pull Requests - Detection And Actioning
Explore the root cause of un-actioned pull-requests, how to detect and remedy (Part 1).
Why Bugs are NOT Technical Debt
why software bugs should not be categorically considered technical debt.
What are all those Warning and Information outputs from a build and why should I care if its not an error?
Reasons why is it important to pay attention to all the warning and information message generated when compiling your code.
Unraveling the Merits of Dependency Injection in Modern Software Development
Dependency Injection aligns seamlessly with the SOLID principles.
Mastering Software Development: A Deep Dive into Trunk-Based Pull Request Workflow
How to implement a pull request workflow within the context of a trunk-based development.
Engineering Practice Layering
Application Layering - Separation of Concerns Architecture Principle
Engineering Practice Naming Conventions
Naming Convention Nuggets of Knowledge and Best Practices
Engineering Practice Nuggets
Nuggets of Knowledge and Best Practices in Software Engineering