Add daily email for 2024-09-07
Find bigs sooner
This commit is contained in:
parent
ed60ab964c
commit
489ec44a75
1 changed files with 26 additions and 0 deletions
26
source/_daily_emails/2024-09-07.md
Normal file
26
source/_daily_emails/2024-09-07.md
Normal file
|
@ -0,0 +1,26 @@
|
|||
---
|
||||
title: Find bugs sooner
|
||||
date: 2024-09-07
|
||||
permalink: daily/2024/09/07/find-bugs-sooner
|
||||
tags:
|
||||
- software-development
|
||||
cta: ~
|
||||
snippet: |
|
||||
Bugs are cheaper to fix the sooner you find them.
|
||||
---
|
||||
|
||||
Whilst speaking with Dave Liddament last week, I remembered a slide I've seen in some of his previous presentations, such as [Effective Code Review][0].
|
||||
|
||||
On the slide is a graph that shows the amount of time needed to fix a bug at different stages of the development lifecycle.
|
||||
|
||||
Fixing a bug is the quickest and simplest when writing code.
|
||||
|
||||
It's harder when being code reviewed or QA or client tested, more so when it's being released, and the most difficult and expensive once it's in the maintenance phase.
|
||||
|
||||
Once it's live in the production environment, there's additional cleanup work to do which adds to the time and cost, and potentially damages your reputation.
|
||||
|
||||
The sooner you can find a bug, the better.
|
||||
|
||||
This is where tools such as automated testing, static analysis and CI pipelines shine and make it easier for you to find and fix potential bugs sooner.
|
||||
|
||||
[0]: https://www.daveliddament.co.uk/talks/effective-code-review
|
Loading…
Add table
Add a link
Reference in a new issue