oliverdavies.uk/content/node.675fbf45-ad63-4685-9f22-e67e17764d9a.yml

76 lines
3.5 KiB
YAML

uuid:
- value: 675fbf45-ad63-4685-9f22-e67e17764d9a
langcode:
- value: en
type:
- target_id: daily_email
target_type: node_type
target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
revision_timestamp:
- value: '2025-05-11T09:00:10+00:00'
revision_uid:
- target_type: user
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
revision_log: { }
status:
- value: true
uid:
- target_type: user
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
title:
- value: "Don't use aliases"
created:
- value: '2024-06-21T00:00:00+00:00'
changed:
- value: '2025-05-11T09:00:10+00:00'
promote:
- value: false
sticky:
- value: false
default_langcode:
- value: true
revision_translation_affected:
- value: true
path:
- alias: /daily/2024/06/21/dont-use-aliases
langcode: en
body:
- value: |
<p>Shell aliases are a good way to increase productivity by shortening long commands, adding additional options to existing ones or creating new ones that even combine multiple commands.</p>
<p>Common aliases are <code>g</code> for <code>git</code>, <code>gs</code> for <code>git status</code> and <code>dr</code> for <code>drush</code>, but they will be different for each person depending on what tools they use and what commands they type often.</p>
<p>Whilst aliases are great for personal productivity, there are times I'd suggest not using them.</p>
<p>If you're giving a demo as part of a presentation or working in a pair or mob, either use the full commands or explain what custom aliases or functions you're running, what they do, and how they differ from the default functionality.</p>
<p>I recently watched a video where someone was using a <code>gc</code> command.</p>
<p>It could have been an alias for <code>git clone</code>, <code>git checkout</code>, <code>git commit</code> or <code>git cherry-pick</code> - just to name a few options.</p>
<p>It could have been something else altogether.</p>
<p>Another approach I use is to have aliases auto-expand and show the full command. This makes it possible for others to see the commands being executed and reminds you, too.</p>
format: full_html
processed: |
<p>Shell aliases are a good way to increase productivity by shortening long commands, adding additional options to existing ones or creating new ones that even combine multiple commands.</p>
<p>Common aliases are <code>g</code> for <code>git</code>, <code>gs</code> for <code>git status</code> and <code>dr</code> for <code>drush</code>, but they will be different for each person depending on what tools they use and what commands they type often.</p>
<p>Whilst aliases are great for personal productivity, there are times I'd suggest not using them.</p>
<p>If you're giving a demo as part of a presentation or working in a pair or mob, either use the full commands or explain what custom aliases or functions you're running, what they do, and how they differ from the default functionality.</p>
<p>I recently watched a video where someone was using a <code>gc</code> command.</p>
<p>It could have been an alias for <code>git clone</code>, <code>git checkout</code>, <code>git commit</code> or <code>git cherry-pick</code> - just to name a few options.</p>
<p>It could have been something else altogether.</p>
<p>Another approach I use is to have aliases auto-expand and show the full command. This makes it possible for others to see the commands being executed and reminds you, too.</p>
summary: null
field_daily_email_cta: { }