34 lines
1.1 KiB
Markdown
34 lines
1.1 KiB
Markdown
---
|
|
title: Slow down to go fast
|
|
date: 2024-02-23
|
|
permalink: daily/2024/02/23/slow-down-to-go-fast
|
|
snippet: |
|
|
Somtimes you need to slow down initially to go faster later.
|
|
tags:
|
|
- software-development
|
|
- automated-testing
|
|
cta: subscription
|
|
---
|
|
|
|
I've recently been improving my typing.
|
|
|
|
![A screenshot of a typing test.]({{site.assets.url}}/assets/images/daily-emails/typing.png)
|
|
|
|
My speed is usually good, but my accuracy is not where I'd like it to be (it's usually around 95%, and I'd like it to be nearer 99%).
|
|
|
|
It may seem counterintuitive, but I need to slow down to get faster.
|
|
|
|
But not focusing on the speed and prioritising accuracy, I'll still get faster as I'm not mistyping as many keys.
|
|
|
|
It's the same when I run.
|
|
|
|
My first few kilometres are slower as I get into the run, find my pace, focus on breathing, etc.
|
|
|
|
## Here's the thing
|
|
|
|
The same can also be said for automation and automated testing.
|
|
|
|
They require some time investment initially but will save time as a project evolves and becomes more complex.
|
|
|
|
You need to slow down initially to go faster later.
|