DaedTech

Stories about Software

By

Being Good at Your Job is Overrated

Let me be clear about something.  This title isn’t clickbait.  I mean it.

But I mean it literally.  Being good at your job is overrated.  We value it too highly.

If you’re a long-time follower of this blog, you might think this is a curious sentiment against a backdrop of advocating for practices like test driven development.  And if you’ve wandered here from somewhere else, you might think this vacuously contrarian.

In either case, relax.

Being good at your job has value.  It’s certainly better than being terrible at it.

But it’s not nearly as important as we think it is, in the grand scheme of things.  The world weaponizes our love of mastery against us at times, causing us to lose sight of other considerations.

I’ll back this claim up with more explicit reasoning a little later.  But first, because I’m back to amusing myself with the blog, indulge me.  I’m going to tell some stories.

Read More

By

DaedTech Digest: What is Slow Travel?

Last time on the digest, I answered a question about whether or not I viewed myself as a tourist.  While answering that question, I used the shorthand term, “slow travel.”  This week, I figure I owe a definition to anyone that hasn’t heard that turn of phrase.

What is Slow Travel?

If you Google this term, you’ll get… interesting… results.  You’ll probably see a lot of quasi-spiritual takes and wishy-washy definitions.  Let’s put those aside, and define it sort of simply.

When I talk about slow travel, what do I mean?  I frequently describe our travels using this term.  To define it, let’s first think about it in the negative.  What would “fast travel” mean?

Fast travel is what you do on your vacations.  You fly to Paris and then you… (deep breath) go to the Louvre, see the Eiffel Tower, check out the Arc de Triomphe, and Notre-Dame Cathedral.  And that’s just day one.  You say, “I’m going to hit everything or die trying!”

That’s fast travel.

It’s what you’re used to as a tourist.  It’s the default.

What is Meaningful (Slow) Travel?

Slow travel is something else, entirely.  To me, it’s the idea of visiting a place not as a vacationer, but as a temporary resident.  You move there for a short period of time.

I reject a lot of the other definitions I see because they dump on tourism.  It’s as though being a tourist were some kind of culturally inferior experience and that you should aspire to be far to cool to do it.

As I said, I view myself as a perpetual tourist.  But I also view myself as a slow traveler.

How do I reconcile this?

Well, by moving to places and spending months there, while also taking in touristic sites.  I reconcile the apparent contradiction by existing somewhere as a quasi-local while also enjoying the sites.  If I were in Paris, sure, I’d see all the places I mentioned.

But I’d also gain an appreciation for the subtleties of being a resident.  What’s it like to go work in a coffee shop for an afternoon?  When is the best time of day to head to the gym?  What’s an extremely uncrowded place with great breakfast?  You get the idea.  Slow travel means getting to know a spot the way you get to know your own neighborhood.

In that vein, here we are conducting a meeting over beers at a place called Sip, in Phoenix.

Picks

  • Last week was a vacation-y kind of week, so picks aren’t as easy.  But here’s a vacation-y kind of pick: Steamworks Brewing in Durango.
  • I just finished the The Fifth Season this week.  Wow, what a great fantasy series.
  • I’m going to throw a nod to Hertz as well.  They aren’t the cheapest, but they are the best, in my opinion.  Always upgrading me, treating me well, and making life on the road easier.

Digest

And, as always, have a good weekend!

By

Does Niching Make You Less Consultative?

Today I’m going to answer a reader question, what with it being reader question Tuesday.  Last time, I talked about how not to let negative feedback get you down.

That seems like child’s play compared to today’s question.  That’s because today’s reader question comes from a reader who is politely asking, “Erik, haven’t you contradicted yourself?”

Don’t get me wrong.  He didn’t put it to me in such direct fashion, as you’ll see shortly.  In fact, he didn’t even suggest contradiction — he was a consummate diplomat about it.  It’s just that his question caused 2018 Erik’s ideas to bang up against 2016 Erik’s.  And it took me a while to reconcile the two.

The Reader Question: Is Niching-Down Counter Productive?

Let’s get to it.  Here’s the question, with a reference to the 2016 post inline.

Thank you Erik for another great article. In “A Taxonomy of Software Consultants”, you say: “[Consultants] are hired in a more general problem-solving capacity. They advance their practice by being known for listening to their clients, tailoring solutions to them specifically, and notching glowing referrals”.

To achieve this, it looks to me that you would have to be sort of a generalist (as opposed to a specialist) in the sense of having to know (a little?) about many things. If so, it would be counterproductive to niche down. Correct?

Often you guys email me (erik at daedtech, and please, send me questions!) with questions or fill out a form on this site.  But this particular question comes in the form of a blog comment on this post, about avoiding the corporate hiring process, written just a couple of months ago.

MrJP has apparently read this blog recently, and also read it back when I made that post in 2016.  He understandably wants coherence in my overall narrative, or at least some kind of explanation.

I’m hoping to offer both today.

Read More

By

DaedTech Digest: I’m a Perpetual and Proud Gawking Tourist

In last week’s digest post, I addressed a question about whether our life of slow travel is one of constant vacation.  (BTW, the digest posts in general chronicle our life of slow travel).  I said that in some ways it is and in other ways, not so much.

This, then, begs the question of whether I not I view myself as a tourist.  Or, a slow tourist, I guess.  People ask questions in this vein at times.

So do you, like, become a local, or are you always kind of a tourist?

I think the reason people ask me questions like this is, perhaps, because of the general uncoolness associated with tourists.  If you go to Paris, there are the locals who flutter between hip, bohemian spots, and then there are the people who don fanny packs and head for the Louvre and the Eiffel Tower.

So which am I?

I am a fanny-pack, Louvre/Eiffel Tower type.  Full stop.

First of all, I’ve never much in my life pretended at any sort of coolness (though I’ve also never actually worn a fanny pack, so there’s that).  It wouldn’t occur to me to head somewhere and then skip the main attractions because I’d look like a yokel.  I am a yokel, and I want to see those main attractions.

But doesn’t the novelty wear off, and you turn into a pseudo-local?

I imagine that you’re thinking this must ease up after a week or two.  But keep something in mind.  You’re imagining the sorts of vacations that you probably take.  You plunk down a bunch of money, wrangle some time off of work, and then manically cram as much sightseeing and experiencing as you can possibly fit into two weeks.

But remember, I don’t travel that way.

I get in on a weekend, see some sights, and then work for a few days.  Then maybe another sight or two, and a few more days.  Rinse, repeat.

So when I’d been in, say, Bay St. Louis on the Gulf Coast for 3 weeks, I’d spent probably three quarters of my time working and a quarter of the time touristing.  Even after a month or two in a place, I have the same capacity for seeing more tourist stuff that you might after 5 days somewhere.

The end result is that we tend to pack our weekends with stuff, even after months.  We spent something like 4 months in San Diego in the past year, and we were still doing excursions to the zoo, various beaches, tours museums, etc.

For us, the tourism never stops.  We live the lives of locals during the weeks, so to speak.  And then we hit all of the surrounding sites in full tourist mode the rest of the time.  I mean, look at this.

It doesn’t get much more touristy than drinking some kind of hurricane out of a grenade-themed yard glass on Bourbon Street.  And we do this kind of stuff readily and without regrets.

Picks

  • For those of you free agents out there, check out the Freelancers Show podcast.  I’m a regular panelist now, so you can hear my unscripted thoughts on all things hustling.
  • I’ve come to love Prime Photos (and video) over the last year or so.  It solves a lot of problems I’ve historically had with photo organization.
  • I haven’t actually tried this one myself, but apparently you can turn Slack into an RSS reader.

The Digest

  • For the NDepend blog, I wrote a post about NLog vs Log4Net.  But instead of comparing their features, I compared how they affect (or seem to affect) codebases that use them.  This was part of my series on code research.
  • For the Rollout blog, I wrote a post on how their recent integration with JIRA takes a step toward bringing a product-focused (startup) mentality to enterprises.
  • And, finally, here’s another in the CodeIt.Right rules explained series.

Thanks for reading, and enjoy your weekend.

By

Value Proposition Guidance for Recovering Programming Generalists

I saw something awesome earlier this week.  Because I’m in the content business, I was trying to explain the concept of “pain, dream, fix” to a client.  It’s a way to write landing pages that focuses on customers and their pain points rather than on product features.  Anyway, in looking for a good explanatory link, I found this gem from Anton Sten.  It’s great advice for landing pages, full stop.  But I’m going to build on it to offer you advice about your value proposition.

Getting a value proposition right is hard enough.  But when you’re used to being a software developer, it’s almost impossible because of how badly everyone teaches us to get this wrong.  So let’s look at the bad advice we get so that we can then start with first principles.

Here’s the picture from the gem of a post I found.  Let’s start there.

The Basics of Pain Dream Fix and the Value Proposition

About a year ago, I wrote about how to start freelancing/consulting as a software developer.  In that post, I emphasized the idea of a “who and do what” statement.  This is a mad lib that takes the form of “I help {who} do {what}.”  This is a value proposition — a way to convince prospective buyers to buy from you.

In the software world, we constantly get this wrong.  And this image illustrates perfectly how we get it wrong.

We tend to talk about our products in giant lists of features.  Or we sell ourselves as an alphabet soup of skills and tech stacks.  And, in doing this, we completely neglect to mention who should care and why.

“Pain, dream, fix” (and this picture of Mario) is a way to jolt ourselves out of our professional solipsism and to start thinking of others.

  1. Pain: Poor Mario is too small and weak to survive in a world of Goombas and Koopas.
  2. Dream: But he could be twice the size he currently is and able to slay his enemies with flamethrower arms.
  3. Fix: All he has to do is eat this flower.

Flower provider value proposition:  We help undersized plumbers kill their foes by giving them super powers.

Seems simple.  But we really manage to get this comically wrong.

Read More