I read the article, but started to get a bit disappointed, when it got to competing and advancing one's career/impact. It espouses a different motivation from the one that drives me.
I'm not against these. After all, it's why most folks get into whatever they are doing. We all need to keep a roof over our heads, and food on the table. We also want to feel good about what we do. It's just not why I do what I do.
I do what I do, directly as a love of the craft, and all my work is an act of creation.
I get up early every morning, and walk a couple of miles. It's usually dark, when I do, and I use the time to sort through what I'll be doing that day. A lot of that "sorting" is a moral and motivational inventory. I figure out what I want to do, and also why I want to do it. If I can't come up with a compelling why, then I have to reconsider the what.
I do enjoy writing. I've done a lot of it[0], and will do more. I don't have a schedule for writing prose. I tend to churn something out once a month or so, but I will sometimes do a couple of articles in fairly quick succession.
I do them for myself. It's nice if people read them, but they really help me to clarify what and why I do, as well as how. Like everything else I do, I apply a lot of polish and refinement; even if I am the only person that will ever read it. One of my habits, is that everything I do, I do as "ship." When even my casual throwaway experiments consist of a level of quality not seen in many large-scale industrial apps, then the stuff I'm serious about, is likely to be fairly robust.
The one daily thing that I like to do, is write code every day. Not just LeetCode (in fact, I never practice that stuff). I like to write "keeper" code, every day, 366 days a year. Of course, I'm not able to actually get that done every day, but I get most days done. My GH Activity Graph is pretty much solid green[1].
I've been at this game a while, and a lot of what I do is almost "instinctual." Basically, "muscle memory." When I'm working on a a project, I don't whip out my GoF Design Patterns book, and figure out which of the Basic Patterns I'll be using, or my copy of Rapid Development, to set out a project plan; I just start writing an OBSERVER or ADAPTER, without bothering to call it that. In fact, the only reason that I tend to use industry jargon, is when I'm trying to leave a trail of breadcrumbs for maintainers. Otherwise, I often make up my own terminology.
I'm a bit "on the spectrum," and tend to live in my own world. It can be a massively productive world, but is insular.
When I write -especially about how I do stuff, it often forces me to get out of "muscle memory," and into the same world everyone else lives in. I have to explain what I do to an audience that is larger than just myself.
So, it's great if people like what I write, but it really doesn't matter that much (at, least, to me).
I'm not against these. After all, it's why most folks get into whatever they are doing. We all need to keep a roof over our heads, and food on the table. We also want to feel good about what we do. It's just not why I do what I do.
I do what I do, directly as a love of the craft, and all my work is an act of creation.
I get up early every morning, and walk a couple of miles. It's usually dark, when I do, and I use the time to sort through what I'll be doing that day. A lot of that "sorting" is a moral and motivational inventory. I figure out what I want to do, and also why I want to do it. If I can't come up with a compelling why, then I have to reconsider the what.
I do enjoy writing. I've done a lot of it[0], and will do more. I don't have a schedule for writing prose. I tend to churn something out once a month or so, but I will sometimes do a couple of articles in fairly quick succession.
I do them for myself. It's nice if people read them, but they really help me to clarify what and why I do, as well as how. Like everything else I do, I apply a lot of polish and refinement; even if I am the only person that will ever read it. One of my habits, is that everything I do, I do as "ship." When even my casual throwaway experiments consist of a level of quality not seen in many large-scale industrial apps, then the stuff I'm serious about, is likely to be fairly robust.
The one daily thing that I like to do, is write code every day. Not just LeetCode (in fact, I never practice that stuff). I like to write "keeper" code, every day, 366 days a year. Of course, I'm not able to actually get that done every day, but I get most days done. My GH Activity Graph is pretty much solid green[1].
I've been at this game a while, and a lot of what I do is almost "instinctual." Basically, "muscle memory." When I'm working on a a project, I don't whip out my GoF Design Patterns book, and figure out which of the Basic Patterns I'll be using, or my copy of Rapid Development, to set out a project plan; I just start writing an OBSERVER or ADAPTER, without bothering to call it that. In fact, the only reason that I tend to use industry jargon, is when I'm trying to leave a trail of breadcrumbs for maintainers. Otherwise, I often make up my own terminology.
I'm a bit "on the spectrum," and tend to live in my own world. It can be a massively productive world, but is insular.
When I write -especially about how I do stuff, it often forces me to get out of "muscle memory," and into the same world everyone else lives in. I have to explain what I do to an audience that is larger than just myself.
So, it's great if people like what I write, but it really doesn't matter that much (at, least, to me).
[0] https://littlegreenviper.com/miscellany/
[1] https://github.com/ChrisMarshallNY#github-stuff