Wednesday, March 4, 2015

"The Free Market(TM) is great until business shows up"*

The first draft of the long-postponed contract overhaul was reviewed yesterday.  When we bought our first house, I learned the fundamental lesson that the property is worth whatever someone is willing to pay for it.  Similarly, there is nothing sacred or "canon" about contracts.  They are what both parties agree that they are when they're signed.  In both cases, buyer's remorse usually has to work at it to impress a judge in the event that things go into litigation.

At a previous job, I also learned that lawyers write contracts for other lawyers.  Which is at least 90% of the problem with contracts.  Unless, of course, you don't use a contract and relations with the client go south, in which case that's 100% of the problem.

One of the revised clauses had to do with both parties agreeing not to recruit each other's employees and/or customers.  As much as I want to give potential clients warm fuzzies (as well as cover my pastey-white dimpled posterior), I instructed the lawyer to nix it.

See, I figure that if it's actually an issue for my potential client, they'll have the great, good sense to negotiate that point.  (Which, incidentally, tells me some very interesting things about their mindset that I otherwise couldn't get at that point in the cycle--always a good thing.)  But having employees/customers poached emphatically does not number among the things that keep me awake at night.

Why?  Because I figure that if someone can smooth-talk someone else out of their relationship with me, then I'm either failing as a boss or a vendor.  Moreover, it calls into question whether that relationship was worth sustaining.  For all I know the "poacher" could be doing me a favour.  It's like the adage, "If he'll cheat with you, he'll cheat on you."  In which case, I wish the poacher all the joy of the new relationship...

But on a larger, philosophical level, I was a bit outraged at the fact that such contract provisions take away the choice of the employee and the customer.  I mean, it's not like either of them has any say--they'll likely never even see that clause, much less sign the contract.  The upshot is that if this sort of language is standard for business contracts, it's basically reinforcing oligopoly and its underlying attitude of entitlement--toward labour as well as markets.

I call shenanigans on that noise.  Maybe such clauses are like the non-compete agreements in the U.S. (basically not worth the proverbial paper they're printed on...and certainly not worth the toner--that stuff's expensive!).  I don't know, and it's likely I won't.

But enforceable or not, people keep letting lawyers pad out contracts (and their billable hours) with such twaddle...probably often enough to buffalo the inexperienced (or those who can't afford to risk even answering a civil court summons).  And so it continues.

Which is yet another reason why I roll my eyes at free market libertarians.  See, if their pipe-dreams even allow government enough power to enforce contracts (iffy), such contracts infringe upon the transparency and frictionless free-flow of information that's supposed to inform the market's "rational actors."  Most especially workers whose wages/benefits could be artificially depressed, or the customers whose prices could be artificially inflated.  Bottom line:  Collusion has the force of law--even in Galt's Gulch. 

And I call shenanigans on that, too.

- - - - -

* Title quotation courtesy of Dennis, who made me LOL with that zinger.

Monday, March 2, 2015

No (real) blog post tonight

I'm finishing my first review pass at a new contract template tonight.  Which not only limits my non-development time, but also renders suspect my ability to use the Queen's English.  After 21 pages of pure legalese, I'll be lucky to write my own name tomorrow without resorting to "herein," "hereunder," "hereunto," "notwithstanding," or similar fluff.

Better luck Wednesday, Gentle Reader.

Sunday, March 1, 2015

Silly Sunday, 2015.03.01: The Programmer "Anxiety Closet"

Fans of the 1980s-ish comic-strip Bloom County will instantly recognise the term "Anxiety Closet."  It was the repository for a lot of pop-culture satire masquerading as neuroses of the overly-sensitive character Binkley.  One Sunday strip gave us a bonus peek into the Anxiety Closets of other characters in the strip--the most memorable being budding hacker/genius Oliver Wendell Jones being chased by a giant slide-rule.

Normally, I keep my nightmares to myself.  Mind you, some nightmares are pretty much public domain.  The "showing up at school/work naked (or trying very hard to get that way)" one?  Check.  The "it's the end of the semester and you realise you've been blowing off a class the whole time" one?  Oh, heck yeah--my subconscious mind has even upped the ante to multiple classes.  (Stupid brain!)

But what if certain subsets of the population also have nightmares in common?  In my case, I mean geeks--specifically programmers.  (I've had SCA-themed dreams, but to date, the only one that turned ugly was that nightmare about the only fabric store in town morphing into the potpourri-reeking fake-flowers-and-wicker-baskets frou-frou kind of craft store.  [shudder]  And I don't even want to think about the nightmares that ComicCon-/GenCon folks could have...)

Anyhoo.

The backstory is that in a couple weeks I'm due to give a presentation on Arduino.  The slides are done, so it's not like I'm behind.  Sure,  I don't have more than a few Arduino projects under my belt at this point.  Yet I personally know one person more qualified than myself to speak on the subject, and he seems to have zero interest in hanging out with Team Coder.  #lesigh 

Basically, it's just like that episode of M*A*S*H where Radar finds an abandoned, injured horse, and Hawkeye and B.J. are pressed into veterinarian service.  Except that first they have to catch the "patient."  
Hawkeye:  "You know anything about horses?"
B.J.:  "I rode a pony once."
Hawkeye:  "You're in charge."  
Moral of the story:  The bar for "expertise" can be set to a very relative--i.e. low--height sometimes.  My apologies for any destroyed illusions there.

So, yeah, I feel kinda like a poser...except I'm probably still in a position to save my fellow geeks a whole bunch of time reading/Googling--not to mention possibly some bling on hardware besides.  Which might explain why last evening's nightmare was about not being able to find the presentation slides on my laptop, rather than about freezing up under the gaze of my peers.

But while curating my resistor collection this morning, I had time to reflect on said nightmare.  Which is when I had a disconcerting epiphany.   It wasn't so much that I was worried about being worried about the presentation.  It was the awful suspicion that this might become an archetype for my dreaming mind.  And, worse, what if this is merely one species in the genus of programmer nightmares?  There are dark, dark regions in the left-brain.  Yet, like any self-respecting D&D dungeon, they somehow support a thriving ecosystem of nastiness:
  • Project requirements include IE6/7 backwards-compatibility.
  • Source control hiccup leaves code in partially merged state, but you don't catch on until you've made a whole pile of changes to your local copy.  #beentheredonethat
  • Zero downloads from the App. Store.
  • You think you're working in the test database, but it's actually the live copy.  #gotthatbadgetoo #twice
  • The "ninja" co-worker your boss hired (over your objections) isn't sanitising inputs...but is rewriting core APIs that s/he doesn't understand...which is clearly most of them.
  • The historical data that you didn't realise was critical when you archived it to tape won't restore.
  • 1:1 assumptions during design magically turn into n:n expectations during beta. #crazytalkinorite
  • User(s) demanding to know why there are "obvious" (to them) bugs in the app. that they agreed to review before sign-off...after they've signed off.
  • Unscheduled system maintenance and/or power outage during a code roll-out weekend.
  •  Apple/Microsoft/Google rolls out an uber-slick near-clone of your world-changing app. the week before you're supposed to close your next round of funding.
So there's that kind of thing lurking about the door of this programmer's Anxiety Closet.  It's probably best not to peer further into the darkness, amirite?

Wednesday, February 25, 2015

Strategic advantage

Being a programmer (or "programmeuse," in local parlance) has certain perks.  One of them being that you can crunch your own data without too much fuss...or even using Excel in ways that the laws of Mathematics and Boolean Logic never intended.  Another being that you can help other folks do the same--with the added bonus that they think you're a genius.

But one definite downside is the frustration of discovering broken code...even when it's code that you didn't write.  Particularly code that's broken in front of the whole Internet 'n Everybody.  By which I of course mean websites with glaring errors.  From the standpoint of someone browsing the site in question, it's easy to blame the lazy/incompetent web developer(s). 

As a programmer, however, one has more tools available for sussing out the real problem.  One only has to submit the "Contact" form (assuming it works) or an email (assuming it doesn't) to let the website owner know:
  1. Hey, there's a problem with your website.
  2. Here is the specific error message (or bug).
  3. This is how you reproduce the problem yourself.
  4. (The biggie) This is likely the root cause.  Debug here first.
I realise that no one truly enjoys learning about a problem, even after accepting Dr. Demming and the doctrine of continuous improvement into her/his heart.   And certainly we live in a world where anecdote, opinion, and ideology carry too much weight in the face of data, experience, and even logic.  The person on the receiving end of that feedback has no way of knowing whether I'm Sir Tim Berners-Lee or whether I've just written my first "Hello, World" web page (if even that).  I get it.

But is a "Thanks for letting us know that you had a problem; we're looking into it" too much to ask?  You'd think not.  But then you'd be wrong.

Please don't think that I'm sulking.  This isn't the first time that this sort of thing has happened to me.  The feedback took less than five minutes of my day:  I don't begrudge that--particularly when it involves keeping my fellow web-mongers honest.  That's to the benefit of the entire guild, right?

Yet I had an actual reason for visiting the website in question--namely, following up on a conversation I had with someone earlier in the week.  (For the record, they're not a client or even a potential client.  That relationship is sacred, and thus off-limits for blogging.)

Now, I don't judge organisations (particularly those that operate on a proverbial shoestring) by website errors...although errors certainly raise some warning signals regarding the client review process.  But I think it's perfectly fair to judge organisations on how quickly they respond to negative (though hopefully constructive) feedback.  Lack of response is symptomatic of any number of organisational ills, including (but not limited to):
  • Generic indifference
  • Bureaucratic sclerosis
  • Chronic under-staffing/under-training
  • Lack of planning/budget for asset maintenance (and websites are assets, dagnabbit!)
  • A culture that penalises mistakes
In my case, the experience turns out to be a silver lining.  It's a very quick-n-dirty way of learning, "These people are (probably) time-wasters."  Someone in another line of work might have to endure several meetings (or even worse) to arrive at the same conclusion.  If, in a couple of weeks, the problem still exists, I can scratch out the "probably."  Or if, in a few weeks more, I'm on the receiving end of their spam...Ooof.  In either case, that five minutes more than paid for itself.

Programmers have an unfortunate reputation of being too code-centric to be successful businesspeople.  But, boy howdy, this is one case when groking the bits definitely provides a leg up on other trades.  [pats self fatuously on head for making it through Programmer School]

Monday, February 23, 2015

A suggestion for lengthening the Provincial purse-string

This afternoon, the Rotary Club and the Chamber of Commerce in Shediac hosted a lunch headlined by New Brunswick Premier Brian Gallant.

Disclaimer #1: I should note that I didn't vote for him in last year's election (because I legally couldn't), and he's so new to the job that I have no idea whether or not I'd regret any vote I might have made.

But I do give him credit for making a fair case for a program that would essentially pay the salary of a young person for the first six months on the job at a qualifying business.

Disclaimer #2:  I wouldn't qualify for the program either as employer or employee, so I don't have a proverbial horse in the race here either.

When I read about the idea, I wrote it off as yet another corporate giveaway.  But after today I'm willing to take a more nuanced view.  If the statistics from other provinces don't have too many asterisks, an ~80% success rate (of keeping the employee working at the same or related field) is more than acceptable.   (Bonus:  Telling those whining about not being able to find ready-made skills or fund the expense of training to put up or shut up would be awesome, IMO.)

As a taxpayer, however, I would hope that there would be penalties for abusing the program.  More importantly, I would insist on an additional and verrrrrrry long string attached to subsidising a half-year of someone's wage.  Namely, that the all data (employee's name excepted) be publicly available on the government's website.

It's not just a matter of accounting to the taxpayers.  The (much) more important public service would be an ongoing record of which employers have a track record of not keeping young employees beyond the six month free ride.  That tells not only potential employees, but also potential vendors which companies are run by people who expect to get something for nothing. 

Please understand that it's not that I think that New Brunswick is rife with that particular species of business owner.  It's just that even one of them can cause serious damage to a small contractor (like myself) or a supplier.  Sadly, this can happen even with signed contracts.  Assuming the aggrieved vendor is able to weather the setback, that cost is ultimately passed on to other, better-mannered clients.  So you'd better believe that checking the public records would be part of my routine due diligence on anyone I'm considering working with. 

Given appropriate penalties for abuse plus public record-keeping, I can, in principle anyway, get behind the proposal.  Because then, not only would it promote business growth, the business intelligence could prevent losses elsewhere in the economy.  Besides, weeding out inefficiencies (in which category I include deadbeats) is what free market capitalism is supposed to be about, riiiiiiiiiight??? 

Friday, February 20, 2015

Frivolous Friday, 2015.02.20: Unsolicited advice to Lenovo

My Gentle Reader and I both realise that history's best, most passive-aggressive form of one-sided "communication" reached its zenith when the 1980s spawned the "open letter."  Granted, once the Intertubes became more or less First-World-Ubiquitous, the open letter--like any luxury-item--became downwardly-mobile.  And thus boring.

But in the original spirit--and on the authority of having been "contractor scum" at a certain company whose initials sometimes stand for "I'm Being Micro-managed" (exceptions made for T.P., M.A., D.P., A.B, and B.W.:  You all know who you are)--here's my advice to the company that took over their PC/laptop product-line.

An Open Letter to Lenovo

It's been a tough week, I know.  Trending Twitter hashtags for two days and counting.  Even Facebook has stopped gawping at the Kardashians and 50 Shades of Domestic Abuse long enough to pay attention.  Bad times.

Bottom Line:  You sold out your users to spammers and left them open to malicious hackers.  All by the cheesy expedient of pre-installing malware and an easy-to-fake root certificate.  I'm sure somebody must have paid you something to go to all the trouble of pimping your (theoretical) customers to spammers.

But, let's face it.  You're not even bush-league when it comes to selling out the people who use your product.  You have to get in line far, far behind Facebook, Google, Twitter, LinkedIn, Instagram, Snapchat, and their ilk for that kind of thing.  I mean, you weren't even bothering to steal passwords, account numbers, or sensitive personal information yourself.  How is anyone supposed to take you seriously?

Your problem is that you're thinking just like a typical I/T company.  Parochial hayseeds!  So narrow-minded, focused on only the eyeballs of the average internet user.  Unlike them, however, you're in a position to monetise so, so much more of your client.  Well, at least until the whole self-driving car thing takes off and then who knows?  That's what should be keeping you up at nightT The possibility of Google having a whole (computing) commuter--or more!--at their mercy.

I tell you, now is the time to execute on your strengths.  You're in hardware:  You can always count on economies of scale.  The future will soon bring haptic keyboards so sensitive you can take fingerprints.  By then, webcams will be capable of emitting low-intensity light.  Either one of those should be worth a fortune when you can sell fingerprints and retina scans by the thousand to identity thieves.

And that's just what current technology could be tweaked to do.  Just imagine the future!  Surely you can (cough!) "partner" (cough!) with the NSA, GCHQ, CSIS, or any sufficiently internetted tin-pot dictatorship to take up the slack for whatever your underfunded, offshored R&D Department won't provide.   For the slight inconvenience of letting them snoop on every twitch your users make, they can reciprocate by opening their books to you.

Think of the possibilities!  Trackpads and touch-screens capable of scanning your customers to the DNA level.  Then it's a mere triviality to wire the button-mouse to deliver a lethal jolt of electricity to young, healthy customers.  Have "sharing economy" contractor already on standby to Uber the corpse to the nearest organ-harvesting facility, and it's like printing money!

And that's just one suggestion for a possible sideline business.  Doubtless, your C-suite has a much more panoramic vision for monetising your users.  Down to the last cell, if possible.  That's why the suits are paid the big bucks, after all.

It's time to pull up your big-kid pants and get to work.  You have a lot of ground to make up before you can go toe-to-toe with the dark-nets or the Russian Mob or anyone else who knows how to use a computer to make money.  Your customers are already paying you a premium for the privilege of being abused--it's time to step up your game.

XOXO,

Doreen

Wednesday, February 18, 2015

Spicing the truth

Over the past weekend, I finished Jack Turner's Spice: The History of a Temptation.   It's alternately hilarious and horrifying.  And, while he belabours his point a bit, it's hard to blame the author:  There's just So Much Stuff to write about in a tale that circumnavigates the globe and spans millennia.  You'll never look at your spice rack--particularly the pepper, cinnamon, nutmeg and clove jars--the same way ever again.

The repeated theme is how the notion of spice has, through the centuries, become conflated with the exotic, sensual, piquant, and even the erotic.  Yet after swooping back and forth in Turner's historical panopoly, it to me seems a shorthand for what human beings do in the face of ignorance.

European merchants (and their suppliers) who traded in spices had a vested interest in keeping the Orient--from whence the spice originated--mysterious, dangerous, and glamourous.  Just like marketing today, it goosed the price--in that day, enough to justify spices' multi-year journey* by ship and pack-animal.

But a generation after Marco Polo's relatively tame account of his trip the Far East, folks still gave their credence to the dragons and mountains of gold invented by the pseudonymous Sir John de Mandeville, who, at best, was reporting second-hand.  (Notable exception:  Christopher Columbus, whose own annotated copy of The Travels of Marco Polo still exists.)

It's no secret that the human mind, like nature, abhors a vacuum.  But the real mystery--to my mind, at least--is how our species prefers to pad that gap with the most phantastical stuffing available.  Occam's Razor is no match for the UNIX Beard of conspiracy theories, escapist fantasies, doomsday porn, organisational solopsism...or whatever pathology the "explanations" serve.

- - - - -

* The distances traveled would doubtless have dulled the taste, justifying the larger quantities that are sometimes observed in medieval recipes.  And, incidentally, putting the lie to the often-repeated myth that spices served to mask the foulness of rotting food.