Stories about Software


How to Become a Management Consultant

Last week, fate (via Hacker News) sent a lot of people to this post, about becoming a software consultant.  This actually resulted in a lot of new readers and followers.  So, first of all, hi to all of the new readers and followers.  But secondly, I’m about due for another consulting post.  So let’s talk today about how to become a management consultant.

This is going to be a guide to charting a course for yourself from working as an individual contributor to a management consultant.  And it doesn’t involve dues-paying or working your way through any degrees or even any other jobs.  It’s a lot more direct than that.

First of All, What Is Management Consulting?  It’s Not as Pretentious as it Sounds

First things first, let’s get to definitions.  I’ve often referred to myself as a management consultant.  (If you want a more detailed history of my consulting, you can find that here.)  Sometimes I call myself a strategy consultant or perhaps an executive consultant.  In a sense, this is all kinda the same thing.

So let’s define that thing.  What is a management consultant?

You could probably find all sorts of definitions out there of varying complexity.  Let’s go with a simple one, though.  First of all, as I’ve explained before consulting is when people pay for your expertise and opinions.  (Not your labor.)  Management consulting is thus a narrower variant of general consulting, with the following two caveats.

  1. You are specifically offering advice to organizational leadership (i.e. “management”).
  2. The advice you offer is related to leadership’s main charter: making organizational decisions and running the business.

That’s really it.  You give advice to organizational management about how best to execute their leadership duties and oversee their organizations.  Naturally, there are a lot of different kinds of advice that you could give, but I’ll get to that a little later.

Should You Become a Management Consultant?

If you’re reading my blog, you’re probably a software developer or at least software-developer-adjacent.  So given the post title and introductory section, you might be looking behind you and wondering if I’m not talking to someone else.  You might just want to write code, either for a company or as a freelancer.

Is this advice really for you?

Yes, it is.  I’ve previously advocated that every software developer become a consultant.  So it’s not much of a reach that I think, if you’re going to become a consultant, you might as well become a management consultant.  Developer Hegemony, aside from being a book, is the crazy idea that software developers should be in charge of software development.  And if we’re going to be in charge of our own industry, it stands to reason that we should know how to run it well enough to offer advice about the same.

So yes, you should become a management consultant.  It’s an excellent way to establish a practice, credibility, industry contacts, and authority.  And the pay isn’t bad, either.

You don’t have to live out of hotels or wear slacks everywhere, or adopt an insufferable vocabulary, either.  Heck, you might not even need to leave fulltime employment, if you get creative.  You just need to establish yourself as an expert in some facet of leadership in the software world.

Read More


DaedTech Digest: The Time Our Slow Travel Lifestyle Broke US Customs

If you follow the DaedTech digst/slow-travel chronicles, you’ve probably noticed a theme.  I answer questions about slow travel and I offer general snippets into our life and what it’s like.

Usually, this probably makes it seem glamorous, or at least interesting.  We go cool places and do cool things.  But there are also aspects of it that can be weird, awkward, tiring, or even altogether negative.  I probably don’t talk about that enough, so let’s change that today with a little story.

A Day Trip to Montreal

We’re spending a month in a town called Newport, Vermont.  If you follow that maps link, you can see that we’re close enough to Canada that we could walk.  Seriously.  It’d be a pretty decent hike, but if we bundled up and made a day of it, we could walk to Canada.

So, naturally, we decided while we were here to visit Canada.  But, walking across the border wasn’t exactly what we had in mind.  So we headed to Montreal, a 2 hour drive, for a long day trip.  And we had a great time the whole day, from morning to late at night when we were driving home after midnight.

At least, we had a great time until we arrived at the US-Canada border and had to go through TSA, driving edition, at the border.

Usually, Border Crossing is a Non-Event For Me

Let me say at this point that I don’t know for sure why the customs guy treated us like we were smuggling black market textiles or whatever.  But I think it happened because our slow travel lifestyle blew his mental stack, which flipped him over into suspicious mode.

Now, I’m not exactly a cross-border commuter.  But I’ve driven across both US land borders enough to have a sense of how it goes for me, normally.  It ranges somewhere between “two halfhearted questions about where I went and why” to “wave indicating not to bother rolling down the window.”

I should say a couple of things at this point.

  1. I realize that there is a lot of “Caucasian male driving a Grand Cherokee” privilege baked into this being my normal experience.
  2. I’m not complaining about the experience I’m about to relate — just musing about why it was different.

And it was certainly different.

At about 1 AM, at the border crossing to Derby Line, Vermont, let’s just say that there isn’t a steady stream of traffic.  In fact, of the 20 minutes or so we spent being grilled by the border guy, the only other car that pulled up was right at the end (and might have been responsible for the merciful end to this bit of geographic bureaucracy).

So it’s a quiet scene.  An out of the way two lane highway giving way to 3 customs-toll-booth things only.

Fear and Loathing at the Border

At first, it seemed mostly unremarkable.  He asked that we roll down the back window, but it was the standard “where did you go and for how long?”

But then things got weird.

I quickly felt like I was in a procedural crime drama, and he was playing the part of Detective Goren.  I realized that he was asking syncopated questions to try to poke holes in my story.  He must have been a Criminal Intent fan also.

“Why did you go to Montreal?”

“Take out your car registration, please.”

“Where did you eat dinner in Montreal?”

“What’s the name of your street at home?”

“Turn off the car, please.”

“What’s the name of your business?”

“What did you say was the reason for going to Montreal?”

“Show me the confirmation for your AirBNB.”

It went on like this for 20 minutes while he popped our back hatch, searched the spare tire compartment, and alternated between three streams of interrogation.  I was on the tired side of 4 hours of roundtrip driving and a full day of walking around and exploring a city.  So I was not at the top of my game, and had a great deal of trouble by the end not making exasperated wisecracks about whether he wanted me to put my liquids in a separate plastic bag.

Why Did This Happen?  I Have a Guess

So, what gives?  As I said, I don’t know for sure.  It could be that he has a randomizer in his booth that alternates between “wave ’em through” and “do your best Porfiry immitation.”

But I think it was my answers to the initial stock questions.

We live in Michigan, theoretically.  And yet, here we were crossing the Canadian border in some remote location in Vermont.  We’d crossed from there for only a day trip, and told him that we were staying in Newport which is, apparently, a tiny town that attracts few visitors.  (The border agent even asked us dubiously, “what made you pick Newport” with a familiarity-breeds-contempt sneer for his surroundings.)

When he asked if were were in Newport for vacation, we exchanged a look and said, “sort of.”  When he asked how long we were there, and we told him a month, he scowled.  And then the syncopated interrogation began.

So, in the end, I think we found ourselves subjected to a protracted grilling and search because our life did not compute to this guy.  This happens in plenty of other contexts.  Heck, it takes this entire blog to explain how our life works.  But it doesn’t all that frequently happen in a context where someone has the ability to turn their own lack of understanding into a mildly threatening problem for us.

Live and learn, I suppose.  Not all slow travel stories are fun or glamorous.  But was it worth it?  It sure was.  Check out this view of Montreal from Mount Royal.


Usually these posts are fun and upbeat, but this one was a little different.  So let’s pick the positive energy back up with some picks.

  • You can’t go to Montreal without having some poutine, which we did.  At a restaurant dedicated to it, which I thoroughly enjoyed.
  • The next day, we wandered down to Burlington, Vermont, where the University of Vermont is.  We ate at a restuarant called Shanty on the Shore, overlooking Lake Champlain.  Lobster rolls and lobster made for a pretty New England-tastic dinner.
  • And, finally, I need to do something internet related, I suppose.  Someone in the Hit Subscribe Slack pointed out Gif Keyboard as a better alternative to Giphy.

The Digest

And, finally, the digest.

  • Here’s another video in our Facebook live series.  This one features a basic and a more advanced description of Hit Subscribe’s business model.
  • This week, we helped Sonatype live blog sessions from All Day DevOps.  Scroll through and you’ll find 4 of them from me, where I listen to the talks, synthesize, and summarize the messages as I understood them.
  • And, finally, I continued to solider on with our site for people to learn about the programming profession.  This is one about the education (or lack thereof) you need to become a programmer.

With that, as always, have yourselves a great weekend.


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


DaedTech Digest: Exploring the Northeast

As with last week’s slow travel chronicle, I’m going to continue with a temporary break from answering reader questions.  (Though by all means, keep firing away with them.  I’ll get back to answering in due time — I just think it’s probably interesting to chronicle as I go, for those interested in this lifestyle).

The Vermont Countryside

Last Sunday, we found ourselves picking our way through underbrush, scrambling up a mountainside on rocks here and there and stepping over roots.  It was muddy, dreary, and generally damp, but the rain held off.

If you want a feel for it, look at the picture below.  We made an afternoon of hiking along Lake Willoughby, with a view of Mt. Pisgah, in Northern Vermont.  In this picture, we were looking out at the lake.  Our hike would take us through those trees and the bottom of the cliff faces on the left hand side.

This has been somewhat emblematic of our time here so far.  Dreary, chilly, incredibly scenic, and lots of natural sightseeing.

The day before, we hiked a bit by Jay Peak, and then just drove around the area, looking at the leaves changing over the scenic, rolling hills and small mountains.  But even on non-weekends, we’ve been making a point to take walks along nearby Lake Memphremagog or else to do short drives.

We’re getting our money’s worth with this excursion, peepling all the leaves there are to peep.

It’s Sightseeing… And Lots of Work

But apart from occasional snatches of tourism, we’ve been working a lot as our business grows in size and scope.  We’ve got a nice, spacious house that’s well appointed, and we’re set up to run the business.  So we do.

We’ve eaten a lot of utilitarian meals and spent a lot of weekdays working from the time we wake up until we go to sleep.  Logistics and errands bring us into town, and we’ve dined out a couple of times.  But mostly, we’re having the sort of weeks you’d have while busy at the office.

No television, no social life or plans, no movie nights, and no casual hobbies.  Such is this stint of slow travel.  We’re either working, or we’re exploring Vermont.

I won’t complain…


  • I’m using Hubspot for a CRM, and it’s been pretty great for a free service.  Oh, yeah, it’s completely free.  So if you have a CRM that needs to grow beyond a spreadsheet, I’d give it a look.
  • I have an Amazon prime membership, and I’ve been listening to Amazon music or Prime music or whatever it’s called this week.  I’ve been pleased with the selection.

The Digest

Hey, whaddya know — I actually did some stuff this week.  For the second straight week!

  • Here’s a Hit Subscribe video from over the summer where Amanda and I (in a hammock) talk about how and why we founded the business.
  • For any of you who are fans of my codebase research series, here’s another one.  I looked at what codebase properties extension methods correlate with.  Do they make your code cleaner?  Not really…
  • Finally, on the Hit Subscribe experiment site, make me a programmer, I wrote a post answering some common questions about how non-programmers interact with a dev team.  This site’s target audience is non-programmers thinking of transitioning into the field, but I don’t imagine that precludes any of you savvy veterans from taking a look.

And with that, as always, have yourselves a good Friday and a good weekend.  And stay tuned next week for an account of our experience driving to Montreal.  (Probably.)


How to Write Software: 5 Lessons Learned from Running Businesses

I used to write software for a living.  I did that for a lot of years, as a matter of fact. And, in doing so, I learned a lot about how to write software.

But I learned this from the perspective of, well, a wage software developer.  Today, I’d like to reflect on how my view has evolved over the last number of years.

Software as a Software Developer versus Software as a Business Owner

As longtime followers of this blog know, I’ve had a meandering career.  I started this blog as a software developer, new to moonlighting.  Eventually I moved into management and then started doing developer training activities.  From there, it was a number of years of consulting.  And finally, these days, I’m mostly running a business that is growing rapidly.

I say all this not to treat you to an unsolicited autobiography, but rather to set the scene and to help explain what I’ve been doing between my last full time software development gig and now.

These days, for Hit Subscribe, I’ve started writing software again.  I don’t do it full time, by any stretch.  But I am building a line of business app used directly by four of us and indirectly by something like 30 people.  So it’s not my primary living, but it’s not trivial either, in terms of importance or scope.

Dedicating some time to this has caused me to reflect on how my perspective has changed.  Don’t get me wrong.  I never stuck my head in the ground pretended “the business” didn’t exist or didn’t matter.  But then again, I never was the business, either.  It was never my money in play.

Now that it is, here are some musings.  And please bear in mind that I’m not teeing these up as lessons you learn.  They are simply how my perspective is different.

Read More