{{ intro.intro }}
+{{intro.cover_intro}}
+
+ {{intro.cover_intro}}
+
+ {{ intro.cover_link_1.text }}
+
I write syntax, and words. I have opinions.
+I've been struggling with this thought for a long time. I've been convinced that I don't like writing code. Perhaps, I'm not meant to write code. Other people seem to be so much more prolific at it. They generate reams of code and move through their work at a good clip. Observationally, I'm the 'problem', right?
\nMaybe. Maybe. However, upon some recent reflection I don't think I am. I'm not sure there is a problem.
\nI finally decided I don't like writing code like other people I know. In my previous post I noted that I find I often think obliquely compared to my coworkers. This has a direct impact on how I think about my code. I wrestle with my code, I struggle to surface clarity as much as possible in my code. If this sounds like an attempt at a brag it's not even remotely that. It's my thought process while I'm working.
\nWhen I write code I try to do a number of things: solve the stated problem (usually from a trouble ticket), make my changes simple to understand for someone else, and make my changes simple to change in the future. I actually consider the last two items far more important than the first. This is because I work on legacy projects. Projects that have been around for 10 years or more. Projects with geological layers of code. If you've worked in a project like this before you already know what I'm talking about. If you haven't worked in a project like this don't worry you will and it's a Learning Experience.
\nLegacy projects, in my experience, are all about maintenance. Code that's been fine and untouched for six years is, without warning, now failing in the most absurd way and it's not obvious why. It turns out what should've have been an unrelated change in another service affected the outcome of a calculation in the six year old code because they were coupled in an obscure way. After hours of work you find it, untangle it, and decouple those two pieces of code. Why were they coupled in the first place? Expediency, inexperience, inattention? All valid, it happens. It is nearly impossible to anticipate how code will be used in the future. I'm not working to future-proof my code, I'm working to make it simple to see how my code works and make it simple to change. The idea that Change is the only constant in software is becoming my personal mantra.
\nMaybe I do like writing code. I love building rules that define how a thing works and then codifying those rules into whatever language I'm working in. I love when my codified rules are simple, as simple I can make them. I love when for just a few minutes there's a moment of clarity in my mind and the code on my screen captures that. I love when I come back to code I've written years prior and it's still clear what it does and how I can change it, not because I remember the code but because it's as simple as I could make it at the time.
\nI love writing code.
\n", + "date_published": "2024-02-10T00:00:00Z" + },{ + "id": "https://401matthall.com/posts/its_the_cognition_stupid/", + "url": "https://401matthall.com/posts/its_the_cognition_stupid/", + "title": "It's the cognition, stupid.", + "content_html": "I encounter many wonderful, helpful people in my day-to-day. They love to share productivity tips and I'm always happy to hear them. I think on occasion people are offended to find out I haven't implemented any of their ideas or suggestions. My peers seem to be confused when I haven't adopted the latest shortcut, key-combo heavy IDE or Vim or Emacs (I'm absolutely not having an Emacs v Vim conversation). I'm always fascinated by how much focus is placed on physical action.
\nSo many people try to help under the impression that my primary struggle is the speed at which I can get information from my brain to my finger tips/code editor. In my case, the limitation isn't the speed at which I can type syntax. In fact, often times taking the time to type all of the syntax including the boilerplate helps me to focus my thoughts. It's taken me a long time to start to understand how differently I think compared to my peers. I'm not slow-witted, I don't think slow. I do organize my thoughts slower than most people. This isn't slow thinking, however. This isn't a lack of articulation or practice in communication. It's a deliberate exhaustive effort to organize my thoughts before I communicate them to avoid confusion for myself and for my audience, even if that audience is only my code editor. Incomplete thoughts aren't thoughts at all for me. They're fragments I don't know what to do with and the effort of hanging on to an unintegrated thought is cognitively expensive. This process is, in fact, work for me. The compulsion to integrate the thought into my existing framework is overwhelming.
\nI'm not failing to type syntax because I don't understand the concept. Rather, I haven't attached all the floating pieces of data to an existing node yet and I'm trying not to lose them. Once everything is connected to an existing point of information I can proceed with the next step which is usually speaking or typing. While I often appreciate the attempts to be helpful the help often fails to address the point of conflict or 'slowness', my brain, not my code editor.
\nThinking is a from-scratch exercise most of the time, at least it is for me. In order to ponder a thing I have to build up a framework either from my memory or my immediate environment (what I can read, hear someone saying, etc) this construction of a framework often takes time and effort on my part and it may appear as though I'm not engaged in the immediate goings on (to some degree, I'm not) but without taking the time to do this I simply can't participate in a conversation, meeting, pairing-session, etc.
\nWhat does it mean for how I work and how I'll work in the future? It means I probably won't try to learn new physical patterns to speed up my work. I find the majority of my work is cognitive. Additionally, I'm not certain working faster is to my benefit and probably not to the benefit of whatever I'm working on.
\nDoes this mean that shortcuts and key-combos are bad? Of course, that's what it means. Shortcut and key-combo users are bad people, they don't give their pets the love and attention they need, and they chew gum while talking in a conference call.
\n", + "date_published": "2023-01-30T00:00:00Z" + },{ + "id": "https://401matthall.com/posts/first_post/", + "url": "https://401matthall.com/posts/first_post/", + "title": "First!", + "content_html": "First posts are the worst. They're the worst to write. They're the worst to read. They're usually brimming with enthusiam for the New Year because when else does someone start a blog or write a second First Post. Ugh.
\nI'm not going to do that to you. I'm not going to do that to me. I want to give informal writing, with an attempt at doing so regularly, a try. I want somewhere to put my thoughts and opinions on things. I want somewhere to excercise my thoughts. That's really what I find writing useful for. Testing, challenging, clarifying my thoughts.
\nAnnnndd we nearly wandered back into the pretentious part of First Posts. That was close. When did we stop adding two spaces after closing punctuation in a sentence? I miss that other space.
\n", + "date_published": "2023-01-28T00:00:00Z" + } + ] +} diff --git a/docs/feed/index.html b/docs/feed/index.html index d1e1647..ab4d783 100644 --- a/docs/feed/index.html +++ b/docs/feed/index.html @@ -5,13 +5,28 @@ -At least not like 'everyone' else.
+ + + #being me + + + #code + + + #coding + + + #problem solving + + + #thinky thoughts + +Why shortcuts and complex key-combos don't save me time.
+Why shortcuts and key-combos don't save me time.
#autism diff --git a/docs/page-list/index.html b/docs/page-list/index.html index e0ea134..d4470d5 100644 --- a/docs/page-list/index.html +++ b/docs/page-list/index.html @@ -22,7 +22,7 @@ - + @@ -75,25 +75,41 @@/tags/first//tags/being-me//tags/autism//tags/code//tags/being-me//tags/coding//tags/problem-solving//tags/thinky-thoughts//tags/autism//tags/first///posts/i_dont_like_writing_code/I've been struggling with this thought for a long time. I've been convinced that I don't like writing code. Perhaps, I'm not meant to write code. Other people seem to be so much more prolific at it. They generate reams of code and move through their work at a good clip. Observationally, I'm the 'problem', right?
+Maybe. Maybe. However, upon some recent reflection I don't think I am. I'm not sure there is a problem.
+I finally decided I don't like writing code like other people I know. In my previous post I noted that I find I often think obliquely compared to my coworkers. This has a direct impact on how I think about my code. I wrestle with my code, I struggle to surface clarity as much as possible in my code. If this sounds like an attempt at a brag it's not even remotely that. It's my thought process while I'm working.
+When I write code I try to do a number of things: solve the stated problem (usually from a trouble ticket), make my changes simple to understand for someone else, and make my changes simple to change in the future. I actually consider the last two items far more important than the first. This is because I work on legacy projects. Projects that have been around for 10 years or more. Projects with geological layers of code. If you've worked in a project like this before you already know what I'm talking about. If you haven't worked in a project like this don't worry you will and it's a Learning Experience.
+Legacy projects, in my experience, are all about maintenance. Code that's been fine and untouched for six years is, without warning, now failing in the most absurd way and it's not obvious why. It turns out what should've have been an unrelated change in another service affected the outcome of a calculation in the six year old code because they were coupled in an obscure way. After hours of work you find it, untangle it, and decouple those two pieces of code. Why were they coupled in the first place? Expediency, inexperience, inattention? All valid, it happens. It is nearly impossible to anticipate how code will be used in the future. I'm not working to future-proof my code, I'm working to make it simple to see how my code works and make it simple to change. The idea that Change is the only constant in software is becoming my personal mantra.
+Maybe I do like writing code. I love building rules that define how a thing works and then codifying those rules into whatever language I'm working in. I love when my codified rules are simple, as simple I can make them. I love when for just a few minutes there's a moment of clarity in my mind and the code on my screen captures that. I love when I come back to code I've written years prior and it's still clear what it does and how I can change it, not because I remember the code but because it's as simple as I could make it at the time.
+I love writing code.
+ + +At least not like 'everyone' else.
+ + + #being me + + + #code + + + #coding + + + #problem solving + + + #thinky thoughts + +Why shortcuts and complex key-combos don't save me time.
+Why shortcuts and key-combos don't save me time.
#autism diff --git a/docs/posts/its_the_cognition_stupid/index.html b/docs/posts/its_the_cognition_stupid/index.html index 50797d5..45c065e 100644 --- a/docs/posts/its_the_cognition_stupid/index.html +++ b/docs/posts/its_the_cognition_stupid/index.html @@ -5,7 +5,7 @@I encounter many wonderful, helpful people in my day-to-day. They love to share productivity tips and I'm always happy to hear them. I think on occasion people are offended to find out I haven't implemented any of their ideas or suggestions. My peers seem to be confused when I haven't adopted the latest shortcut, key-combo heavy IDE or Vim or Emacs (I'm absolutely not having an Emacs v Vim conversation). I'm always fascinated by how much focus is placed on physical action.
@@ -60,12 +60,11 @@Thinking is a from-scratch exercise most of the time, at least it is for me. In order to ponder a thing I have to build up a framework either from my memory or my immediate environment (what I can read, hear someone saying, etc) this construction of a framework often takes time and effort on my part and it may appear as though I'm not engaged in the immediate goings on (to some degree, I'm not) but without taking the time to do this I simply can't participate in a conversation, meeting, pairing-session, etc.
What does it mean for how I work and how I'll work in the future? It means I probably won't try to learn new physical patterns to speed up my work. I find the majority of my work is cognitive. Additionally, I'm not certain working faster is to my benefit and probably not to the benefit of whatever I'm working on.
Does this mean that shortcuts and key-combos are bad? Of course, that's what it means. Shortcut and key-combo users are bad people, they don't give their pets the love and attention they need, and they chew gum while talking in a conference call.
-Why shortcuts and complex key-combos don't save me time.
+Why shortcuts and key-combos don't save me time.
#autism diff --git a/docs/tags/being-me/index.html b/docs/tags/being-me/index.html index 6668b7a..71a8114 100644 --- a/docs/tags/being-me/index.html +++ b/docs/tags/being-me/index.html @@ -22,7 +22,7 @@ - + @@ -52,7 +52,32 @@At least not like 'everyone' else.
+ + + #being me + + + #code + + + #coding + + + #problem solving + + + #thinky thoughts + +Why shortcuts and complex key-combos don't save me time.
+Why shortcuts and key-combos don't save me time.
#autism diff --git a/docs/tags/code/index.html b/docs/tags/code/index.html new file mode 100644 index 0000000..801556d --- /dev/null +++ b/docs/tags/code/index.html @@ -0,0 +1,103 @@ + + + + + + +At least not like 'everyone' else.
+ + + #being me + + + #code + + + #coding + + + #problem solving + + + #thinky thoughts + +At least not like 'everyone' else.
+ + + #being me + + + #code + + + #coding + + + #problem solving + + + #thinky thoughts + +At least not like 'everyone' else.
+ + + #being me + + + #code + + + #coding + + + #problem solving + + + #thinky thoughts + +At least not like 'everyone' else.
+ + + #being me + + + #code + + + #coding + + + #problem solving + + + #thinky thoughts + +Why shortcuts and complex key-combos don't save me time.
+Why shortcuts and key-combos don't save me time.
#autism diff --git a/posts/i_dont_like_writing_code.md b/posts/i_dont_like_writing_code.md new file mode 100644 index 0000000..78c93cc --- /dev/null +++ b/posts/i_dont_like_writing_code.md @@ -0,0 +1,26 @@ +--- +title: I don't like writing code... +description: At least not like 'everyone' else. +date: 2024-02-10 +tags: + - being me + - code + - coding + - problem solving + - thinky thoughts +layout: layouts/post.njk +--- + +I've been struggling with this thought for a *long* time. I've been convinced that I don't like writing code. Perhaps, I'm not *meant* to write code. Other people seem to be so much more prolific at it. They generate reams of code and move through their work at a good clip. Observationally, I'm the 'problem', right? + +Maybe. *Maybe.* However, upon some recent reflection I don't think I am. I'm not sure there *is* a problem. + +I finally decided I don't like writing code like other people I know. In my previous post I noted that I find I often think obliquely compared to my coworkers. This has a direct impact on how I think about my code. I wrestle with my code, I struggle to surface clarity as much as possible in my code. If this sounds like an attempt at a brag it's not even remotely that. It's my thought process while I'm working. + +When I write code I try to do a number of things: solve the stated problem (usually from a trouble ticket), make my changes simple to understand for someone else, and make my changes simple to change in the future. I actually consider the last two items far more important than the first. This is because I work on legacy projects. Projects that have been around for 10 years or more. Projects with geological layers of code. If you've worked in a project like this before you already know what I'm talking about. If you haven't worked in a project like this don't worry you will and it's a Learning Experience. + +Legacy projects, in my experience, are all about maintenance. Code that's been fine and untouched for six years is, without warning, now failing in the most absurd way and it's not obvious why. It turns out what should've have been an unrelated change in another service affected the outcome of a calculation in the six year old code because they were coupled in an obscure way. After hours of work you find it, untangle it, and decouple those two pieces of code. Why were they coupled in the first place? Expediency, inexperience, inattention? All valid, it happens. It is nearly impossible to anticipate how code will be used in the future. I'm not working to future-proof my code, I'm working to make it simple to see how my code works and make it simple to change. The idea that Change is the only constant in software is becoming my personal mantra. + +Maybe I do like writing code. I love building rules that define how a thing works and then codifying those rules into whatever language I'm working in. I love when my codified rules are simple, as simple I can make them. I love when for just a few minutes there's a moment of clarity in my mind and the code on my screen captures that. I love when I come back to code I've written years prior and it's still clear what it does and how I can change it, not because I *remember* the code but because it's as simple as I could make it at the time. + +*I love writing code.* diff --git a/posts/its_the_cognition_stupid.md b/posts/its_the_cognition_stupid.md index 700abec..d2d8e57 100644 --- a/posts/its_the_cognition_stupid.md +++ b/posts/its_the_cognition_stupid.md @@ -1,6 +1,6 @@ --- title: It's the cognition, stupid. -description: Why shortcuts and complex key-combos don't save me time. +description: Why shortcuts and key-combos don't save me time. date: 2023-01-30 tags: - autism @@ -20,5 +20,3 @@ Thinking is a from-scratch exercise most of the time, at least it is for me. In What does it mean for how *I* work and how I'll work in the future? It means I probably won't try to learn new physical patterns to speed up my work. I find the majority of my work is cognitive. Additionally, I'm not certain working faster is to my benefit and probably not to the benefit of whatever I'm working on. Does this mean that shortcuts and key-combos are bad? Of course, that's what it means. Shortcut and key-combo users are bad people, they don't give their pets the love and attention they need, and they chew gum while talking in a conference call. - -[@401matthall](https://twitter.com/401matthall) \ No newline at end of file