DaedTech

Stories about Software

By

DaedTech Digest: How to Make Money While Vagabonding?

This is an interesting premise for the week’s digest post.  I say this because I think it arose from somebody misunderstanding why and how I have money.

There is a small population segment that slow travels and makes a living blogging about the same.  But we are not part of that segment, weekly digests about our adventures notwithstanding.  We make money in a different way.  Still, let’s answer the question.

How do you make money while vagabonding?

First up, there are some people that don’t.  These include retirees and the independently wealthy.  This ins’t terribly interesting, though, so let’s quickly move one.

Next, you have people that work in some kind of gig capacity.  Do a gig for 3 months, take a new one elsewhere.  This isn’t what most think of as slow travel, per se.  But, depending on the demand for services, people working this way can control their destination and live places a few months at a time.

Alright, now here’s our bucket: the remote worker.  My wife and I own a location-independent, pure-remote business.  We can work from anywhere, so we do.  As we travel, we tend to work schedules that would look familiar to the workaday nine-to-fiver, albeit with more flexibility.  But remote work could also apply to wage employees that are remote, as well as to folks that simply contract or freelance.  As long as you can work from anywhere, you make money doing that work.

And, finally, you have the people that I mentioned earlier, who are travel bloggers.  Sure, they’re a subset of business owners with location independence.  But, for them, the vagabonding itself is kind of a job.  Not so for the rest of us.

So the money itself can really vary.  But what stays consistent is the interesting assortment of destinations.

Picks

  • I’ve been listening to an audio book called the Pumpkin Plan, and it’s about how small business owners can avoid a situation of barely keeping their heads above water indefinitely.  Of particular interest to my audience might be how he talks about ranking clients and cutting bait on bad ones.
  • Here’s a podcast I listen to called The Business of Authority.  It covers a range of topics, but it’s good stuff if you’re an established freelancer or consultant looking for advice on how to grow from there.

The Digest

  • For those of you who are fans of my research posts over at NDepend, here’s another one.  I examined the relationship between code comments and the descriptiveness (length) of method/type names.
  • Hot off the presses!  I recorded a solo episode for the Freelancers show about how to target the C-suite was a freelancer.
  • And, finally, here’s a Facebook Live where Amanda interviewed me while I was standing in a lake.  This was done in the same vein was one of our author spotlight interviews.  Except the lake part.  We don’t normally do that with the authors.

Have a great weekend, folks!

By

Employment Teaches You How Not to be a Free Agent: You Have Stuff to Unlearn

Recently, I was doing something that occupies a surprising amount of my time these days: using LinkedIn for lead gen.  This involves researching companies, connecting with people, and, occasionally, consuming LinkedIn.

It was in that latter capacity that I stumbled across this post, from Jonathan Stark.  I nearly spit out my coffee.

It’s funny, right?  But the thing is, it’s also true.

Seriously.  I could probably write an entire post about why telling prospects that you’re “passionate” is a bad idea, both from a positioning and a realpolitik perspective.  But that’s not what I want to talk about today.  At least, not entirely.

When I read this, an idea for a blog post snapped home in my mind.  It had been kind of rolling around, not fully formed.  But then I read this and the basic thesis struck me.

Learning to be a good employee is tantamount to learning to suck at being freelancer/business owner.

Of course, this isn’t exhaustively true.  Very basic qualities like competence, diligence, and “EQ” will serve you well anywhere you go.  But in many important ways, the instincts you develop while advancing as a corporate employee serve you absolutely terribly if you decide to go off on your own.

Read More

By

DaedTech Digest: Deciding How Long We Should Stay

It’s been a few weeks now since the last DaedTech digest.  In that one, I chronicled the last little bit of our trip to Vermont.

We haven’t gone anywhere since then.  Not really, I mean.  We’ve been back and forth to Illinois a few times, visiting family and taking care of logistics.  But that hardly merits a slow travel chronicle.

So let’s go back to answering questions about slow travel until we embark on our next adventure.

How do you decide how long to stay in the places you go?

I’ve seen a lot of family and old friends of late, so I’m plucking a question that one of them recently asked.  They wanted to know how we decide what amount of time to spend somewhere.

Well, on the short side, that’s simple.  We only go somewhere for at least a month.  If you’re under a month, sites like AirBNB and VRBO charge the sorts of rates per night that you see on the site.  But at a month or more, a monthly rate kicks in, which often cuts the nightly rate in half or so.  This means that such a place, while not as economical as a year lease on an apartment, is somewhere in between that and a hotel.

As for the duration of stay, that’s historically depended for us one one of two things:

  1. When does the weather change (i.e. when does winter end)?
  2. Do we have somewhere to be or something to do?

If we’re somewhere to escape the cold, we leave in something like May, to make sure that we really do miss the cold.  But other stays, like our recent one in Vermont, end when we have something to do.  This might range from some kind of plans with a family member or friend to, well, Christmas.

And that’s really all there is to it.  We stay as long as we feel like or until we have reason to go elsewhere.  And we don’t always know how long we’re going to stay when we leave.  Sometimes we book a month or two and then extend.

That was the case when Amanda took this picture of me in Ocean Beach, San Diego.  It was bonus San Diego time.

Picks

  • I just recently started using a new ad blocking plugin for Chrome called uBlock origin.  I’d been dealing with some flakiness from the Ad Block plugin, and this one has been great.  Lower memory footprint and it blocks more things.
  • We’d been trying forever to sell our townhouse in Illinois, and we finally managed to with the help of a great realtor named Christine.  We’d had the place on the market for almost 2 years without luck.  When we listed with her, she got us an offer that we accepted within 2 weeks.  If you’re in the Chicago suburbs and want to sell, give her a call.

The Digest

And, as always, have yourselves a great weekend.

By

What Do You Know That People Would Pay You For?

I actually started this post last week, in what was shaping up to be a long one.  Instead, I decided to spin the lead-in off into its own post about staff augmentation.

In that post, I covered a decent amount of ground, but I’d like to focus in on two main points about the software industry.

  1. We have a curious habit of calling ourselves “consultants” when we’re not.  In other words, our industry is perhaps the lone industry where we refer to labor as “consulting.”
  2. The main determining factor in what we call software development engagements is who manages the software developers.

This lead up, expounded upon mainly in the previous post, leads to an interesting question.

If Software Development is Knowledge Work, Why Do We Act Like It’s Labor?

I talk frequently on this blog about knowledge work and surrounding concerns.  Here’s a good working definition of knowledge work.

The term “knowledge worker” was first coined by Peter Drucker in his book, The Landmarks of Tomorrow (1959). Drucker defined knowledge workers as high-level workers who apply theoretical and analytical knowledge, acquired through formal training, to develop products and services.

They include professionals in information technology fields, such as programmers, web designers, system analysts, technical writers, and researchers. Knowledge workers are also comprised of pharmacists, public accountants, engineers, architects, lawyers, physicians, scientists, financial analysts, and design thinkers.

Software development certainly seems to fit the bill.  I mean, it’s literally mentioned repeatedly in this definition.  And yet, perhaps uniquely among all of these vocations (except maybe technical writing), software developers are paid for what we do with our hands, rather than what we know in our heads.

Don’t believe me that this is a curious diversion?

Then why does it find its way past even how people bill for our work and into our job titles: “architects” to do the “big picture thinking” and software developers (laborers) to bang out code?  Or into our self-selected metaphors, such as the strained guild concept, where we’re not experts offering diagnoses, but “craftsmen” building digital cathedrals or horseshoes or whatever?

Read More

By

Happy Thanksgiving, 2018!

Hello there, DaedTech readers!  In what has sort of been an annual Thanksgiving tradition (I do it some years), I’d like to wish you all a Happy Thanksgiving!  As in this past years, please enjoy this drawing by my wife and business partner, Amanda.  And please enjoy your holiday.

For those outside the US, Thanksgiving is a federal holiday that celebrate on the 4th Thursday of November that sorta celebrates colonialism… but is really mainly an excuse to see your family.  This is not to be confused with “Black Friday,” which is a more recently conceived, unofficial holiday that celebrates the joy of bludgeoning people at Walmart to get discounts on IPads.  Black Friday occurs the day after Thanksgiving.

The more I think about it, the less I want to delve into the history of this, and the more I want to enjoy a day of not working and seeing family.  So, enjoy the drawing of a cat’s take on Thanksgiving, enjoy your celebration, and know that I’m thankful to have so many engaged readers.