Software Development is a Business Tactic, Not a Profession

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.

Don’t worry.

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.

• Today: I run a tech-serving a content marketing business.  So, yeah…

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!”

Read More

Hustle or Work-Life Balance: What’s the Right Answer?

I have a rich annual tradition that I only just became aware of this year.

Every year, around this time, Apple has some kind of conference or announcement or something.  It’s the time of year when, for a day or two, an iThing getting smaller or losing a USB port makes everyone absolutely lose it and flood my news feed with opinions for a few days.

And I’ve only this year realized that this seems to happen annually and that it’s probably a pattern.  But every year, including this one, I’ve mustered a strong, festive sense of complete apathy.  I think.

The Nights and Weekends Platitude Heard ’round the World

This year, the event rocketed into my awareness not because of some new product or service, but because half of my Twitter feed started retweeting things like this:

Tim Cook just said thank you to all the Apple employees “who gave up their nights and weekends from their families” to build all the shit they just showed.

Fuck…that…shit.

— Dan Kim (@dankim) June 3, 2019

It’s heart-warming how many people are noting @tim_cook’s celebration of working nights’n’weekends and refusing to applaud extractive sacrifices. Overwork isn’t cool, especially not on a regular, expected, and self-imposed schedule. Deal with a crisis, sure. A release ain’t that.

— DHH (@dhh) June 4, 2019

Whoah, okay.  Curious, I spent some time looking for the transcript of wherever he said this, but to no avail.  I couldn’t even find a video of it.  (Though I did learn that this annual apple thing is called “WWDC.”)

The closest I could find was this Tweet with a quote, from someone who, presumably, had listened.

Tim Cook’s closing words: Thanks to all the people “giving up nights and weekends”. If this is Apple’s work ethic that’s really a shame ☹️😣

— Alex 🌚 (@alexmuench) June 3, 2019

So, from what I gather, Tim Cook, during the course of the obligatory shout-out to the little people, gave them thanks for working their little tails off during their little nights and their little weekends.  And the world subsequently had opinions.

I Have Deep Ambivalence about Hustle Culture

Long time readers of the blog might remember this viral post about “sucker culture.”  I let a CEO, “Victoria,” have it for bemoaning her employees’ lack of desire to work extra hours for no pay.

In fact, I’ve written at length about the standard corporate hierarchy and how it involves a cultural tricking of many people into over-performance in exchange for no value.  Obviously, in the posts and in my book on the subject, I don’t treat this as a positive.

And, perhaps most compelling of all, I own a business with employees.  And, along with my wife and partner, hold work-life balance as a non-negotiable governing principle.  We view this as humanistic and simple, good business.

If we’re building a company that requires heroic efforts to exist or scale, we’re building something unsustainable and with artificially inflated value.  It’s the corporate equivalent of wrestlers cutting weight just before a weigh-in.

And yet, I work a lot.  Last week was a 4 day week, following Memorial Day weekend, and I managed to work a 49 hour week from Tuesday to Friday.  In my management consulting life, I used to put in 40 hour weeks, run the business that would become Hit Subscribe in the evenings from my hotel, and still do things like write a book.  And sandwiched between Sunday night and Friday night flights home.

So what’s my deal?  Am I a hypocrite?  Some kind of would-be martyr?  I’m honestly asking myself these questions non-rhetorically, and this blog post is my attempt to figure out the answer.

Because I think it’s none of the above.  I think, instead, that I’m fortunate enough to have continually hacked my career into situations where I both enjoy and benefit from work, thus rendering it all a sort of work/hobby mish-mash.

Read More

The Renaissance of the Problem Domain as a First-Class Concern

Hey, look at that — I’m writing a blog post again!  Seriously, apologies for the lull, but, hey, life happens.

Enough of that, though.  Let’s dive into some realio-trulio, software related content.

I Read an Interesting (Horrifying) Tale This Morning

Lately, instead of starting my day blearily looking at my phone and the emails that have trickled in while I slept, I’ve been starting each day with unstructured reading and chatting.  I randomly read my feed, talk to people on Slack, watch a Youtube video, or take some research flight of fancy.

Anything goes as long as it’s:

1. Not completely mindless
2. Not directly related to work I’ll do

I can’t recommend this practice enough, especially for the self-employed set.  It stimulates creativity and sort of gets all of the things that normally distract me out of the way.

But I digress.  The real point of this mini-anecdote is to say that I read a blog post from Uncle Bob Martin this morning.  It’s a compelling read, as his posts generally are, and it talks about the recent Boeing crashes.

Here’s something that jumped out at me, though, somewhat oblique to the narrative, and relatively mundane in an otherwise pretty grim tale.

Rather, programmers must [have] intimate knowledge of the domain they are programming in. If you are writing code for aviation, you’d better know a lot about the culture, disciplines, and practices of aviation.

And then, this, at the end:

We have to know the business domains we are coding for.

Huh.

Read More

Staff Augmentation is as Staff Augmentation Does

I’m in the process of drafting a post entitled “What Do You Know That People Would Pay You For?”  But what I’ll put here in this post, combined with the material for that one, are shaping up to be long.  So I think I can carve off an initial, coherent point here about staff augmentation.

That one figures to be uplifting.  This one?  Perhaps not so much.  But I think it’s important to establish a premise.

If you write code in exchange for a salary, you’re either staff or staff augmentation, depending on who signs your paychecks.

Now, for those of you that have worked for product/service companies with a software component, you’re probably shrugging and thinking “yeah, no kidding, I’m staff.”  Ditto those of you who have toiled in a cost-center capacity, maintaining some internal software the company would sooner eliminate.

But those of you that work for custom app dev agencies are probably feeling a little huffy, since most places that sell custom app def (i.e. staff augmentation) go out of their way to state righteously that they most certainly DO NOT do staff augmentation.  Bear with me, though, all of you.

I don’t actually think there’s anything wrong with staff augmentation.  In fact, I think it’s a substantially better model, in most cases, than staff.  In accordance with the spirit of Developer Hegemony, I think we, as an industry, should strive to move from staff to staff augmentation, at least as an initial step.

Read More

Good Companies Don’t Ask You to Share. They Make You Want To

“So please, go ahead and share this with your social networks.”

I imagine that your company says stuff like this to you all the time.  So frequently, in fact, that you’re probably sorta numb to it.

• Hey, we’re hiring!
• Our company was just nominated for Who’s Who in American High School Students Companies!
• We’ve got a new product release coming up!
• Steve is talking at a networking event!

“So please, go ahead and share this with your social networks.”

It’s an Innocuous Request… And It’s Also Okay If This Rubs You Wrong

I can remember the first time I heard this.  Before, I’d spent the first part of my career working in companies that manufactured products, with software as only part of the equation.  Because of the developers’ relative anonymity and the relative newness of social networks, I never encountered any request like this.  It simply wouldn’t have come up.

But this particular year found me working at a shop selling app dev (and calling this “consulting”).  With the people as their product (or at least the people’s labor), the individual contributor software developers had more of a prominent role.  And so the request came.

“So please, go ahead and share this with your social networks.”

I don’t remember what it was that we were supposed to share or tweet or whatever the verb for that on LinkedIn is.  The company may have been asking for help with recruiting, marketing, sales, or something else.  It doesn’t matter.

For our purposes here, what matters to me is that this rubbed me the wrong way.

I didn’t really know why at the time, and it’s taken me years to start to understand why.  I wasn’t embarrassed to work there or anything.  It was… a place that gave me money in exchange for labor. And that’s a thing that most people do.  The request wasn’t onerous and it didn’t compromise my morals and ethics in any way.  Even the fact that it was a request to do something of value for free occurred to me, but didn’t bother me.

Still, though.  I didn’t like the request and didn’t do it.

Years later, this request is probably much more common.  For the rest of the post, I’m going to expand on why this might rub you wrong, why that’s okay, and what should happen instead.

Read More