DaedTech

Stories about Software

By

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

By

DaedTech Digest: Notes from the Road in Vermont

It’s Friday, which means it’s time for yet another slow travel blog/digest post.  If you’d like to catch up on the category, you can read previous editions here.  I’ve mainly been answering questions people ask me about the slow travel lifestyle.  But, since we just packed up did a mini-move to Vermont, I figured I’d chronicle the experience in more live fashion.

On the Road: Heading to Vermont

As I’ve described in the past, we have a house on a lake in Michigan.  That feels to us like an idyllic spot, so we tend to stay there in the summer, almost slow-traveling at a property that we own.

So for us, there’s summer and then there’s 9 months of slow travel season.  And now, it’s slow travel season.

So last Saturday, we packed up for a month of travel, pulled all of the boats out of the lake, and got ready to go.  Sunday morning, we packed up the car, wrangled our cats. and hit the road.  Since the drive to Newport, Vermont takes around 15 hours, we split it into two days, stopping at a cat-friendly hotel in Rochester, New York.

Once you’re past Eastern Ohio, the whole drive along the southern coast of the Great Lakes becomes a pretty one.  The trip treated us to rocky countryside, leaves starting to change, rolling hills, and lots of woods and small towns.

Settling in for a Month of Slow Travel

And now, here we are, settled and resuming normal life.  Unpacking typically takes an evening, with complete settling in happening after a day.  With slow travel, there’s always the initial supply run as well.  This consists of groceries, whatever you’ve forgotten to pack (there’s always something), and stuff you discover you need.  For instance, I forgot to pack a keyboard and mouse, so I bought those at a local Walmart, along with a wifi range extneder because the router here is kind of iffy on one side of the house.

Once settled, we really try to absorb the local everything.  Amanda went out to a local grocer last night and got gourmet Vermont maple syrup, some kind of locally made steak/chicken rub, and even this maple-flavored sparkling water, which I admittedly view with some skepticism.

We’re on a lake, so, in spite of some rainy weather since arrival, I’ve made a point to jog along its shore and into the town.  We’ve gone for day and night walks, discovering a worryingly friendly skunk that lives underneath a neighbor’s house, and getting to know what shops and restaurants are nearby.  And, I took immediate and full advantage of the view I have for the next month while enjoying my morning coffee.

Picks

And with that, let’s do some picks.

  • Last week, Amanda found this app, GoodRX, which let her get a prescription for like half the price.  I can’t speak directly to it myself, but that sort of savings means it’s probably worth a look.
  • I’ve signed up for a trial of ahrefs, a keyword research and SEO tool, and I’ve found it to be extremely helpful in finding good post topics.

The Digest

And, hey, look at that, the internet has published some actual blog posts that I’ve written this week.

Happy Friday and, as always, have yourselves a good weekend.

By

Narrow Niche: When is Narrow Too Narrow?

I think I’m going to abandon the idea of “reader question Tuesday,” or any particular day.  I’ll keep writing reader questions, but, in keeping with my announcement of blogging for fun, I’ll just post them whatever day of the week I feel like.  So today, a Wednesday, let’s do a reader question about a narrow niche.

So, let’s get into it.  Here’s the reader question.  It’s in response to a point I made about how to build an audience.  Specifically, I said to find problems that people Google and offer solutions.  In response, a reader asked the following.

One of the issues I face when I think of writing anything on a topic is that I immediately find lots of other articles discussing the same thing. But if we write about a specific question we could have more [readers to ourselves].

However, how do we know if a question is common enough?

The Narrow Niche in Content and in Specializing

Let’s consider what he’s asking here.  Take a topic like, say, test driven development.  If you Google test driven development, it’ll seem like every imaginable topic has been covered.  But if you Google “cobol TDD,” the results quickly turn to the sound of crickets.  So write about TDD in Cobol and get readers, right?

Well, if there are any.  I say this because I have a number of tools that estimate the quantity of searches for a term in a given month.  And it appears that almost nobody is searching for posts about TDD with Cobol.  Hence the reader question.

How do we know if the question is a common enough search to be worth writing about?

Well, at the simplest, most tactical level, you could install the Keywords Everywhere plugin and see for yourself.  Here’s what Google shows me, for instance.

But that’s a pretty short-sighted answer.  The real question here is a deeper one.  How do you know if a series of topics is worth writing about, and how do you pick your focus for a blog.  And, for all of you free agents and aspiring free agents, how do you pick a specialty and competitive advantage?

You want a narrow niche, or you’re just a miscellaneous, generalist laborer.  But if you narrow it too much, you might have no audience or customers.

Read More

By

DaedTech Digest: Packing Edition and What We Take

As I mentioned in a recent digest post, we’re heading to Vermont in a few days, where we’ll stay for a month.  Since mentioning that, we’ve gotten questions about leaving our house unoccupied and about what packing is like.  Since I answered the former last week, I’ll answer the latter this week.

What Does One Pack for a Month?  Necessities

I’m going to try to resist the impulse to turn this post into my packing list.  Instead, I will simply mention that I make a packing list.  I use Trello for the packing list, and tend to reuse the same one each time we vagabond.  So, protip, I guess.

But, in terms of what we take, let me lay it out in broad strokes.  Amanda and I each pack a large duffel’s worth of clothing, representing about 10 days to 2 weeks’ worth of clothes.

This can be surprisingly lightweight or a little bulky, depending on the weather.  Not so much cold vs. warm, but how variable.  For instance, we’re going to Vermont for October, which means that we might encounter anything from t-shirt weather to frost and snow.  This means we need to pack more stuff.  If we were just going to, say, the Equator or to Alaska, we could bank on one kind of weather and pack more lightly.

From there, we pack certain necessities.  This includes our cats and their stuff.  It also includes my fairly meaty computer setup.  That actually speaks for most of the cargo space in our Jeep, with the rest going on top.

And Then, the Other Stuff

Work, animals and clothing is the core of our packing efforts.  But we also bring some things we could live without.  I always haul around a bag of electronics, which includes a few Alexa devices, a cordless phone, power strips, and other stuff I tend to like having.  Amanda brings a small suitcase thing full of makeups and nail polishes and such.

After that, the other main thing that we bring is some foldable, economical furniture.  This includes a folding chair and a folding table, in case the place we’re going doesn’t have a serious desktop setup. (We’ve learned from experience after buying these things upon arrival, when the AirBNB doesn’t have a desk.)  We also, space-permitting, will bring things like little bedside fans or humidifiers/dehumidifiers.  Again, things we’ve purchased after arrival and learned to take with.

And, speaking of buying things after arrival, I’ll close with this note.  You’ll always buy some stuff after arrival.  Assume that you’ll spend a couple hundred dollars when you get onsite, buying fans, cheap tables, coffee makers, or other things that aren’t there and that you realize that you need only after seeing they aren’t there.

And that’s packing.

Picks

  • This is kind of a weird one, but I want to throw a nod to Quest Diagnostics.  Following a routine physical, I had to go for routine blood tests, and that experience can be anything but routine.  But with Quest, I made an appointment online, showed up a little early, and they had me in and out in 5 minutes or so.  Remarkably efficient.
  • This past weekend, my old Fitbit dipped to an unacceptable battery life after a respectable 2.5 years.  So we went out looking for one during the middle of our Hit Subscribe outing in Chicago.  At a Target, at like 9 PM on a Saturday, we found a Fitbit Flex 2 on clearance for $29.99.  It’s lightweight, holds a good charge, and has been making me pretty happy so far.
  • Speaking of Hit Subscribe, I can’t help but do a slight bit of homer bragging.  We’ve been growing and bringing on more people and we now have our first employee that isn’t me or Amanda.

The Digest

I’m kind of light on written things of late.  I’ve done a few, but clients have yet to publish them, and I’ve been doing more video and audio content, lately.  So, in that vein, I’ll offer some new media for the digest, all of which are videos.

  • First, here’s a Youtube video on the Hit Subscribe channel where I describe topic planning for clients.
  • Amanda and I have also been doing Facebook Live videos about running a remote business.  Here’s the first one we ever did, a couple of months ago in Durango, CO.
  • And here’s the second Facebook Live (pardon the wind).

And, as always, have a great weekend, folks!

By

Coding as the Boss: My Story of Developer Hegemony

Last night (this morning), I clicked “publish” at about 3 AM and went to bed.  Now, those of you who follow this blog probably assume that I clicked “publish” in WordPress, firing off a 3 AM blog post.

Not so.

I did this in Visual Studio, where I published a little web app called El Dorado to Azure.  I source control the thing in Github and I publish to Azure, where it serves as a little line of business application for me and some of the staff at Hit Subscribe.  And, while a Visual Studio publish isn’t exactly state of the DevOps art, it gets the job done.

The significant thing here isn’t any of the techs that I’m using.  It’s also not the fact that I was up late coding, nor is it the purpose of the app.

What matters here is that I own a non-trivial and growing business and that I’m also writing code.

The Classic Management Track vs Technical Track Conundrum

Years ago, I wrote a blog post in which I told a story of something most enterprise-y/corporate programmers encounter sooner or later.  It’s the “where do you see your career going, management or technical” question.

Choose wisely, young programmer.  Down one path, expense accounts and Gantt charts await.  Down the other, UML diagrams, and… well, probably also Gantt charts.

I could never really wrap my head around this dichotomy.  I mean, I get that furiously banging out code and leading departments are somewhat divergent activities.

But I never understood why the line blurred so little and so infrequently.

I poked around the internet a little to see if this was still true, and I think it mostly is.  I found some posts like this one, talking about the coding dev manager.

But this has always seemed like just taking the role that most companies call “architect” or “tech lead” and having people actually report to it.  That just kind of kicks the can down the road slightly.

If you’re a “coding manager,” you’re probably in a fairly vertical, tech-focused organization where line managers still don’t really think about “the business.”

Are Technical and Business Savvy Mutually Exclusive?

So this begs an interesting question.  Are technical savvy and business savvy mutually exclusive?

Oh, I mean, don’t get me wrong.  I’m not honestly asking whether techies can become startup CEOs or whether leaders with f-you money couldn’t learn to code.  Of course those talents can both exist in the same human being.

What I’m asking is whether or not someone can do both of these things meaningfully, at the same time.  Can someone run a department (beyond a “tech-lead-y” line management role) and also have legitimate business reasons to bang out code, and do it halfway decently?

I have a hypothesis that the answer is yes.

Yes, people can run non-trivial organizations while having good reason to code.  And no, applied, simultaneous technical and business savvy are not mutually exclusive.

Read More