aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarc Coquand <marc@mccd.space>2024-01-23 13:49:51 -0600
committerMarc Coquand <marc@mccd.space>2024-01-23 13:49:51 -0600
commitebbdacce30ee511e1133aeed5842941a35959c44 (patch)
treecba5430316a1605b0367c2bbc62c471cf661c878
parent094466c7c5ce7b5aa82fd5ef6fb0ecd38ab4fac9 (diff)
downloadmccd.space-ebbdacce30ee511e1133aeed5842941a35959c44.tar.gz
mccd.space-ebbdacce30ee511e1133aeed5842941a35959c44.tar.bz2
mccd.space-ebbdacce30ee511e1133aeed5842941a35959c44.zip
Update title of remote work article
-rw-r--r--posts/remote-work.njk4
1 files changed, 2 insertions, 2 deletions
diff --git a/posts/remote-work.njk b/posts/remote-work.njk
index 0ae7999..0969021 100644
--- a/posts/remote-work.njk
+++ b/posts/remote-work.njk
@@ -1,6 +1,6 @@
---
layout: post.njk
-title: A Busy Bee's Guide to Remote Work
+title: A Guide to Remote Work
tags: post
date: 2023-09-22
---
@@ -163,4 +163,4 @@ As a programmer, I have invested a lot of time into learning the tools that I us
<h2> A side note for programmers</h2>
<p>
In many ways, I think about communication mediums like data structures. While it is tempting to use hashmaps and arrays for every problem, they are not necessarily the best representation of the data we are working with. Instead, I can use sets, trees, enums, relational structures to more easily solve my problem. The same logic applies to how we communicate. Synchronous is basically the array of communication, easy and works for most forms and so we try to apply it to way too many forms of communication. Different platforms make certain types of communications easier or harder, so I try to think about which one makes the most sense for the message. How will I query it in the future?
-</p> \ No newline at end of file
+</p>