Code review is the practice of having other engineers examine a change before it is merged. Reviewers check correctness, design, security and readability, and share knowledge along the way.
CI/CD is the practice of building and testing every code change automatically, then releasing changes that pass through a repeatable pipeline. It shortens the gap between writing code and running it in production.
Static application security testing (SAST) analyses source or compiled code for security flaws without running it. It usually runs in the developer's editor or the CI pipeline.
Technical debt is the future cost created when software is built in a quicker or simpler way than it should be. It shows up as extra effort, bugs and slower delivery every time that code is touched later.
Version control is a system that records every change to a set of files over time. Teams use it to collaborate, review history, compare versions and restore earlier states when something goes wrong.
The definition of done is a shared checklist of conditions every piece of work must meet before a team calls it complete. It makes "finished" mean the same thing for everyone.
Open source describes software whose source code is published under a licence that lets anyone use, study, modify and share it. Projects are often developed in public by communities of individuals and companies.
A clear proven process, that delivers
You've seen our ideas - now go deeper.
Discover more insights, guides, and engineering practice.