opdavies/oliverdavies.uk
1
0
Fork 0
Code Issues 1 Pull requests Projects 1 Releases Packages Wiki Activity Actions

Remove http://default from content

Browse source
This commit is contained in:
Oliver Davies 2025-07-16 12:00:00 +01:00
parent 025aaf3be2
commit 76ed8e141b
392 changed files with 525 additions and 525 deletions
Download patch file Download diff file Expand all files Collapse all files

4
content/node.a8f06c67-81eb-471c-9081-0648c9400e27.yml
View file

@ -66,13 +66,13 @@ body:
<p>It could be a small refactor - renaming a variable or class name that makes some code easier to read or removing some commented-out code that isn't doing anything other than adding visual clutter.</p>
<p>It could be updating some documentation or <a href="http://default/daily/2022/09/23/adrs-technical-design-documents">writing a technical document</a>; if you keep those in your version control repository, that would help you implement the following change or to make the documentation clearer for the next reader - whether that's you or someone else.</p>
<p>It could be updating some documentation or <a href="/daily/2022/09/23/adrs-technical-design-documents">writing a technical document</a>; if you keep those in your version control repository, that would help you implement the following change or to make the documentation clearer for the next reader - whether that's you or someone else.</p>
<p>Committing something at least once a day creates a different mindset to "I'll write everything and push it when it's done".</p>
<p>It makes you break up large tasks into multiple smaller ones and set mini-deadlines for yourself. I used to do the same when I commuted to work on a train and had a task for a freelance project to complete before I arrived. I used to think, "What can I start, finish and commit before I get there?" instead of leaving something incomplete.</p>
<p>You don't need to push your change to mainline. If you use the <a href="http://default/daily/2022/11/30/ship-show-or-ask">"Ship, Show, Ask" approach</a> then you could commit to a temporary branch that you either merge yourself once you know it passes the checks, or to show or get feedback from other team members.</p>
<p>You don't need to push your change to mainline. If you use the <a href="/daily/2022/11/30/ship-show-or-ask">"Ship, Show, Ask" approach</a> then you could commit to a temporary branch that you either merge yourself once you know it passes the checks, or to show or get feedback from other team members.</p>
<p>Practicing this becomes a habit, and if you're doing test-driven development and committing after every passing test or refactor, you'll find yourself pushing numerous changes a day.</p>