Any regular followers of DaedTech may have noticed that I’ve dropped off the map of late with new content. Now, before I go any further, please understand that I’m not petering out with content, holistically.
I think you’ll pry my (metaphorical) pen from my cold dead hands. I can’t not write.
But the break here is semi-intentional. I say “semi”, because it started with me not having time to post one week, and then realizing that I wasn’t overly excited about any of the content I was queuing up. This led to an unannounced decision to take some time off and gather my thoughts about what I want to address on this blog.
I’ll get to a justification of my premise that software development isn’t a profession. But that operating thesis is fundamentally inextricable from my background and my current wrestling with topics.
A Brief History of DaedTech
I won’t make this section a long, self-indulgent tour of my life. Rather, here’s a quick-hitter history of how the subject matter here has evolved on this blog over the last decade.
- Early-DaedTech: I was a line level programmer (mostly .NET). So I wrote about .NET programming topics, office politics, and general programmer life.
- Mid-DaedTech: I was in leadership and starting to side hustle. Here, I trained .NET/Java devs, so those topics remained, but topics about business/leadership/hustle started to displace them.
- Recent-DaedTech: I was an IT Management Consultant. At this point, granular tech topics dropped off the map, and everything started to be about free agency, career, and hustling.
Which brings me to today.
The Topical Conundrum
Whether I’ve written with some broader purpose in mind, or just written about whatever strikes my fancy, I’ve always drawn topic inspiration from my day-to-day work. And this made for relevant content in the tech world, since my journey was IC software developer –> IT leader –> (software) strategy consultant.
But as what I’m doing is increasingly about running a growing business and marketing, a gulf is emerging. Certainly, readership of this blog has evolved over the years, with those most interested in my early .NET unit testing how-tos dropping off, and more folks interested in freelancing stopping by. But I now face an interesting conundrum.
- I could start to write about the trials and travails of being an executive at a growing, tech-facing marketing business. But this would probably create a complete audience overhaul, and, l like writing about the software world.
- Or, I could keep writing about the things I wrote about as a software developer/leader/trainer. But the day to day of that recedes further in my rearview mirror all the time.
Oh, don’t get me wrong. I still write code and have opinions about software. I still occasionally consult on codebase assessments. I’m not worried that I’ll become technically illiterate or something.
What I’m worried about is writing about the industry more as an antiseptic observer than as a participant. I’m worried that an increasing number of posts I might write would invite declarations of “easy for you to say!”