oliverdavies.uk/content/node.675fbf45-ad63-4685-9f22-e67e17764d9a.json
2025-05-14 00:36:23 +01:00

100 lines
No EOL
4.6 KiB
JSON

{
"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": "\n <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>\n\n<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>\n\n<p>Whilst aliases are great for personal productivity, there are times I'd suggest not using them.<\/p>\n\n<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>\n\n<p>I recently watched a video where someone was using a <code>gc<\/code> command.<\/p>\n\n<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>\n\n<p>It could have been something else altogether.<\/p>\n\n<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>\n\n ",
"format": "full_html",
"processed": "\n <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>\n\n<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>\n\n<p>Whilst aliases are great for personal productivity, there are times I'd suggest not using them.<\/p>\n\n<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>\n\n<p>I recently watched a video where someone was using a <code>gc<\/code> command.<\/p>\n\n<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>\n\n<p>It could have been something else altogether.<\/p>\n\n<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>\n\n ",
"summary": null
}
],
"feeds_item": [
{
"imported": "1970-01-01T00:33:45+00:00",
"guid": null,
"hash": "d77f4c3aa58ffc20e26976b05b6332a5",
"target_type": "feeds_feed",
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
}
]
}