Finding my copy of BASICball, re-reading my cute little grade-school comments (”Screen math is stupid”), remembering  anecdotes about what was going on at the time (”Our class gerbil is coming home with me for Thanksgiving break!!!!”), caught me up in an atypical wave of nostalgia. And in that wave, in looking back – really thinking about everything I have written over the years: millions upon millions of lines – that two things really stand out as being key to my success: Worse is Better, and Modularity is Ultimate.

I’ll write more about those things, I’m sure, but for now: Happy 20th Anniversary BASICball v6.0.

I just aged a bit, happily.

3 lbs boneless chicken breasts
1 lemon, cut in half
1/4 cup ghee, melted
4 large garlic cloves, chopped fine
thumb-sized piece of fresh ginger, peeled and chopped fine
2 tbsp ground paprika
1 tsp ground cinnamon
1 tbsp ground cumin
1 tsp ground coriander
1/2-1 tsp ground chili powder
1/2 tsp ground cloves
1/2 cup plain yogurt
4 drops red food coloring
2 drops yellow food coloring
2-3 small (or one large and seeded) chili peppers, chopped fine
14 oz can diced tomatoes
1 cup heavy cream
1/4 cup fresh cilantro (chopped)
salt
pepper

Preheat oven to 400F (will be using top rack). Place cleaned chicken in large glass bowl  and  stab repeatedly with pairing knife. Rub in 1/2 lemon and 1/2 tsp salt. Add in 1/2 of the chopped garlic, 1/2 of the cumin, 1 tbsp paprika,  and all of: ginger, yogurt, food coloring, cinnamon, coriander, chili powder, cloves. Mix with your hands until everything is evenly coated up to your elbows. If prepping ahead, this mix can go into the fridge for up to a week just fine.

Put chicken on cookie cooling rack over a solid, rimmed cookie sheet (dripping on the bottom of the oven are not fun). Some people claim a roasting pan works too. *shrug* With turkey baster, or a spoon if you’re boring, splurt 1/2 of the ghee over the top of  the chicken mess. Bake for 45 minutes. Broil for 10-20 minutes until top coating visibly blackening in spots (not burning!!). While broiling, make the sauce (next paragraph).

In large cast iron skillet, add remaining ghee over high heat until drops of water cause sizzling. Add remaining garlic and chili pepper, sauteing for 30 seconds or so. CAREFULLY add cream, diced tomatoes (with liquid) – ghee will be hot and addition of liquid may causing flashing!! Stir in remaining spices except cilantro (a few grinds of salt and pepper, too). Reduce heat to medium and simmer uncovered, stirring regularly,  for about 10  minutes or until sauce visibly thicker.

After chicken is done, remove and allow to cool for a couple minutes. Cut into small chunks and add to sauce.  Cover and reduce heat to low, cooking about 5 minutes.

Serve with rice and bread, sprinkling cilantro and a lemon wedge around plate edges for garnish and extra seasoning.

Serves 4. Prep time about 1 hour (serial). Cook time 70-85 minutes.

If you apply for jobs being vetted by morally superior -word removed- who pine for the “old days” of hunting witches in Salem , probably yes.

If not, then no. As someone who has done a lot of consulting for various gambling-related businesses, I can tell you that any software development company should prize former casino/gambling-related coders (that leave on good terms). It takes a lot of pedantic coding, edge-case handling, and vociferous documentation to make that industry run “right”, and those skills are hard to bake into someone.

I can’t speak to other countries, but in the US there are very few jobs that will – in and of themselves – cause you to get passed over for prospective employment. Except maybe working for the Revenue Service. We really don’t like them.

I’ve seen a lot of concerts, and only really bother writing about the exceptional ones, but wow- The Hip at the NAC on Saturday was hands-down one of the best shows I’ve attended. Mid-sized venue, great seats, the usual antics, ringing ears the next day (I didn’t need that auditory spectrum, anyhow), and one horrendous case of vertigo (my left ear is telling my brain I’m falling to the right, which causes me to fall to the left trying to compensate) today: All the hallmarks of a great live concert!

Appetizer: Wine Poached Pears

Recipe was from an old friend of mine (from memory), melded with one from a cookbook for precision.

1 1/2 cup red wine or burgandy
1 cup raw sugar
2 tbsp lemon juice
2 cinnamon sticks
6 cloves (whole)
4-6 pears (whole, peeled)

In a pot combine all ingredients except the pears over med-high heat until boiling. Reduce to low and simmer, covered for 3-5 minutes (should be noticeably thickened). Lop off the bottom of each pear so they will sit upright on the plate for serving later.

Add the pears on their side if possible, and cook uncovered for about 15 minutes or until tender, turning frequently.

Remove the pears to small serving plates, upright. Bring reserve sauce to a boil, uncovered, over med-high/high heat, until reduced to a thick glaze, ~5-8 minutes. Remove cinnamon sticks and cloves with tongs. Drizzle over pears and serving plate.You may serve chilled if climate dictates.

Serves: 6. Prep time: ~2 minutes.Cook time: 25 minutes.

Salad: Goat’s Medley w/ Walnuts

I can’t overstate the value of baby spinach, dandelion greens, and clover sprouts. Simply the best salad you can make. The ratios can be varied for taste.

1/2 lb baby spinach
1/2 lb dandelion greens (shredded or chopped)
1 bunch radishes (sliced, chopped, or shredded)
2-3 carrots (sliced or shredded)
1/2 lb sun-dried tomatoes
1 1/2 cups freshly cracked walnut pieces

Combine. Toss. Serve with your favorite version of raspberry vinagrette.

Serves: 6-8 humans, or 1 goat or llama. Prep time: 20-15 minutes.

Entree: Peppercorn-rubbed Filet Mignon

Purists and book-wise chefs would crucify you for rubbing down a tenderloin filet with anything more than simple salt. I’m neither.

Peppercorn Rub

Regular peppercorns can be subbed-in here, but it changes the dynamic. This rub is great on any cut of beef. Double, triple, etc. as needed. Keeps well in sealed container for several weeks. Omit sugar until just in time, to keep for several months.

2 tbsp szechuan peppercorns (whole)
2 tbsp coriander (whole)
1/2 tbsp raw sugar
1 tsp allspice (whole)
1 tsp sea salt

In iron skillet, over grill or med-high burner, cook szechuan peppercorns and coriander until you can smell them well, about 2-3 minutes. Remove from heat, combine with rest of ingredient in a food processor or spice grinder. Pulse-grind until evenly-blended but coarse.

Coats 4-6 filet mignons lightly. Prep time: ~2 minutes. Cook time: 3 minutes.

Grilled Filet Mignon

If you don’t know the difference between tenderloin cuts, that’s ok. Filet mignon is the tip of the tenderloin: very small, and very pricey. I recommend 2″ cuts because that yields about 7 oz of meat. If you can’t afford all mignons (will run you about $50 for 6 little cuts) then you might want to purchase a whole tenderloin, which any reputable butcher will gladly slice up for you: 1″ cuts of the upper tenderloin with a single 2″ mignon at the bottom will run you about $40, but net 6 good-sized steaks plus the mignon. Do not buy packaged filets wrapped in bacon. If you’re going to pay for tenderloin, make sure it’s being chopped fresh just for you.

4-6 2″ thick filet mignon cuts of tenderloin beef
or
4-6 1″ thick upper tenderloin cuts

Preheat grill on high. Trim visible fat from filets. Rub down filets by hand with peppercorn rub, coating evenly but lightly. Turn grill down to medium. Meat should be flipped every 5 minutes. Should be served medium-rare (135 degrees), medium (145 degrees) at most… but well-done brutalizations are also possible (165 degrees). All temperatures are taken at the center of the meat.

Serves: 4-6. Prep time: ~5 minutes. Cook time: varies by thickness and doneness, 7-25 minutes

Dessert: Raspberry Tart

This lovely was made from scratch by my lovely, following a copyrighted recipe I can’t legally reprint here. Excellent ending to a great meal.

AMEN

I really want to call attention to some of the finer, most important, high-impact parts of his essay. The focus of this is management, but if you’re in a relationship, or friends with a knowledge worker, you’re generally just as likely to be impacted for all the same reasons as someone in the same IT establishment.

R-E-S-P-E-C-T

Those whom they do not believe are worthy of their respect might instead be treated to professional courtesy, a friendly demeanor or the acceptance of authority.

My closest friend once warned a newcomer, “if Matt was consistently nice to you, you’d be irrelevant.” This is not a concious thing, but it is very real. Arguments, seemingly unprofessional behaviour, witty banter, are all ways of negotiating decisions and divining truth and logic. No knowledge worker wastes energy or logic on people that aren’t worth the investment. We’ll take bullets for those we respect, but wouldn’t lift a finger for those we don’t. That respect is earned by a confluence of aptitude, attitude, and appreciation. I’ll fall over myself trying to help a bright person who bakes me cookies, or someone who admits they’ve got a problem and is willing to do what it takes to solve it. But bright and ungrateful, or troubled and unwilling to learn – forget it. I’ve got better things to do.

IT pros are [not] antisocial. On the whole, they have plenty to say.

The biggest misconception you can make is that a knowledge worker’s lack of engagement has anything to do with being anti-social. Sure, there are some socially awkward people in any group, in any industry, but they’re not the mass. Again, it has to do with the value of communication. Don’t expect a network architect to ramble on about dulcimer trees and virtually redundant paths to your HR director- They can assess, instantly, the subject-matter competency of their audience and will prefer to say nothing and hover by the punch bowl over engaging people who won’t understand anything they have to say. This works the other way as well. Knoweldge workers don’t care about accrual systems nor the intricacies of handling the corporate Christmas Fund.

Self-organization

IT pros always and without fail, quietly self-organize around those who make the work easier, while shunning those who make the work harder, independent of the organizational chart.

Look at your IT group:

• Do they hang-out voluntarily outside of work? Knowledge workers don’t generally leisure with anyone they don’t respect.
• Do they invite managers to do things? A manager who is being included by a team has their respect.
• Do they invite managers outside of their chain-of-command to do things? You may have a synergy there you’re not realizing the potential of.
• Who do they eat with? Meal time is leisure time. Geeks don’t eat with people that give them indigestion.

The more synergies you see within the above dynamics, the more likely you have a successful team on your hands. If you observe these groupings happening across group-lines (server guys and network guys… network guys and programmers… helpdesk and programmers, whatever), that’s a pretty good indication you’ve got good geeks, and they’re gelling well . If you notice team members heading for the door the moment work is “over”, never involved with other members, probably they’re being shunned and you’ve got some decisions to make.

Minesweeper Consultant, Solitaire Expert

Doctors are a close parallel. The stakes may be higher in medicine, but the work in both fields requires a technical expertise that can’t be faked and a proficiency that can only be measured by qualified peers.

I’ve never met a knowledge worker that cares about degrees or certifications, theirs or others. Your MIS or MBA earns you no credibility. Your A+ or MCSE won’t even get you a second glance. Experience, demonstrable skill, and respect are the only currencies that matter. The worst thing a manager, co-worker, or anyone else can do is try to fake it. Fraud is always a bad decision, generally generates more work, and smacks of irresponsibility- None of those things a knowledge worker will appreciate.

It’s Lupus

While everyone would like to work for a nice person who is always right, IT pros will prefer a jerk who is always right over a nice person who is always wrong. Wrong creates unnecessary work, impossible situations and major failures.

Would you prefer a nice doctor that cuts off your left leg to cure your broken right thumb? Or someone who barely acknowledges you exist, but seemingly effortlessly diagnoses your rare condition, and sets you on the correct treatment before walking out of the room, never to see you again? If I had a nickel for every time my mother said “no one likes a know-it-all”, I would have retired at 17. Your uber knowledge workers are always right. They are. They have to be. If they weren’t, you wouldn’t keep them around. Why would you? What’s the point in an asshole who’s wrong frequently/all the time? Showing that you have confidence in their decisions, and will back them up in between the time that they say “we should do X” and X is finally proven to be “right” means the world to them, and gains you major credibility. Throwing out illogical arguments, or pedantic edge-cases that are nothing more than theoretical CYA, loses you major credibility.

It’s not about being right for the sake of being right but being right for the sake of saving a lot of time, effort, money and credibility.

Separating the Wheat from the Chafe

If someone has to constantly be taught Computers 101 every time a new problem presents itself, he can’t contribute in the most fundamental way.

Team members that aren’t competent and are unwilling to learn need to be reassigned away from knowledge workers. They’re poisonous, and over time will drag down morale and cause retention problems.

Strong IT groups view correctness as a virtue, and certitude as a delivery method. Meek IT groups, beaten down by inconsistent policies and a lack of structural support, are simply ineffective at driving change and creating efficiencies

As a manager, if you have a group that actively works to maintain the status quo; not changing or evolving with the times; not improving or increasing services – then you have a problem. The problem could be you, or it could be the group, or it could be a bit of both.

Knowledge workers strive to create efficiency and to evolve their own role. Good knowledge workers will seek out new services to offer, or new ways to do old things. Great knowledge workers will continuously automate their “old job” such that every 6…8…15 months their current job looks nothing (relatively) like their old job. If they’re not doing this (re-read Self-organization, too), it’s time to shake things up.

If the problem is you, shore up your support for them. Make a real, sustained effort to get in their corner- to show them you have their back. It’s amazing how quickly a good group can turn around with a little consistent, positive focus. An obtuse group won’t respond at all to TLC.

Some people will still think I spelled chaff wrong.

You’re Paying Money For That?

IT pros are sensitive to logic — that’s what you pay them for. When things don’t add up, they are prone to express their opinions on the matter, and the level of response will be proportional to the absurdity of the event. The more things that occur that make no sense, the more cynical IT pros will become.

Nothing sets a knowledge worker off faster, more viscerally, or with less ability to restrain, than making an illogical or over-valued acquisition. If your team says “we can do that with open source software” or “we could do that in-house”, you need to listen. What they’re really saying is “only an idiot would go and spend money on shit… Money you’re not putting into our salaries”. Knowledge workers want to provide great services. They’re not going to suggest a product that stinks, or won’t meet the needs- it would reflect poorly on their decision-making skills. The more upset they are, the more you need to listen. That nice shiny new pair of shoes with all the bells and whistles will cost you dearly in morale. Dearly.

Pointless administravia like meaningless “evaluations”, paperwork, etc. are similarly likely to receive push-back.

What executives often fail to recognize is that every decision made that impacts IT is a technical decision. Not just some of the decisions, and not just the details of the decision, but every decision, bar none… It can cost an organization literally millions of dollars.

When HR goes out and buys a new HR system that’s “easy to use” and “won’t burden your IT people” and wizzbangwow without consulting IT on several levels, this is a bad thing. Of course, when you bring in your knowledge workers, and they say “this really shouldn’t be purchased”, you need to listen to them. Again, I’ve never met a knowledge worker that gives a care about their own workload: they care about making sound decisions, and helping the organization succeed. HR may be impressed with the marketing glitz surrounding the nice shiny new pair of shoes with all the bells and whistles, but that doesn’t mean the organization should acquire it.

Management Behaving Absurdly

Good IT pros are not anti-bureaucracy, as many observers think. They are anti-stupidity.

Sun-Tzu said (out of order) “Defeated warriors go to war first and then seek to win, while victorious warriors win first and then go to war”.

Mat-Thew said “A manager takes a collection of resources and accomplishes work, while a leader fosters accomplishment by inspiring their resources toward work”.

If you feel your knowledge workers have problems with authority or don’t respect you because you’re bureaucratic, you could be right. However, Occam’s Razor tells us that if you see this problem in more of your workers than you don’t, the problem isn’t them… It’s you.

Even marginal knowledge workers acknowledge the need for, and willing to participate in, logical bureaucracy. They want to get paid, so they account for their hours and report them. They want to have a record of work, so they will use ticketing systems. They want the organization to succeed, so they will provide truthful expert knowledge when called upon (a manager would call this a “meeting”), as long as there is logical purpose for the provision.

Arbitrary or micro-management, illogical decisions, inconsistent policies, the creation of unnecessary work.

If you have personnel who need micro-management, they’re not knowledge workers – but smart (ostensibly) people there to collect a paycheck. You’ll also notice through self-organization, that they’ll be on the “outside”. Micro-managing knowledge workers is detrimental, because it steps on self-organization, shows lack of understanding, and most damningly- it causes a knowledge worker to question your motives, and increases the likelihood you’re a credit whore.

Executives expect expert advice from the top IT person, but they have no way of knowing when they aren’t getting it. Therein lies the problem.

As a manager, nothing will create an image problem for you faster than if those over you don’t feel they can get the answers they need from you. If executives are talking directly to your subordinates, you’re getting side-doored, and are becoming irrelevant. Once this hits a critical mass, expect to be relocated or removed altogether. IT managers must have awareness of what’s going on now, what technologies are being used, and where your knowledge workers are leading into tomorrow. If you don’t know those things, or can’t communicate them up the ladder, you’re obsolete.

And make sure all your managers are practicing and learning. It is very easy to slip behind the curve in those positions, but just as with doctors, the only way to be relevant is to practice and maintain an expertise. In IT, six months to a year is all that stands between respect and irrelevance.

I can’t expand much on this. If you’re managing systems people, learn systems- constantly. Programmers? Network analysts? Doesn’t matter- you need to stay current with their world. You do not need their depth of knowledge, but they need you to understand that C is more than the third letter of the alphabet, that linked-lists should never be used outside of a computer science class, that flow control is good but flow constraint is bad, that X is something more than the 24th letter of the alphabet, and you damned-well better know the non-paged memory limit of a 32-bit system architecture.

Who?

IT pros would prefer to make a good decision than to get credit for it.

I was having coffee with a colleague earlier this week (discussing management pitfalls, ironically), when a woman I took classes with many years ago walked up and said “I didn’t know you worked here!” My colleague smiled at her and said “You really just made his day by saying that”. It’s true. Knowledge workers want to be involved in sound decisions, and furthering goals, mostly eschewing credit as long as internal respect orders are maintained. Knowledge workers will chew on their tongues until they bleed to avoid  saying “I told you so” (although it’s always on the tip of their tongue, and do come out, occasionally); they’ll credit “the team” when a spotlight is on them.

If you have people that say “I” instead of “we” frequently, there are two reasons. Either the person is there for just a paycheck, or there is concern that management will take credit for their work. Don’t do that. If you look at self-organization, you should be able to spot where they stand.

Making Management Matter

The primary task of any IT group is to teach people how to work. That’s may sound authoritarian, but it’s not.

Left to their own devices, non-knowledge workers (inside, and outside of IT) will maintain the status quo. They’ll do the minimum necessary to collect their paycheck, and never work any smarter. As a manager, it’s critical that you realize the value of your knowledge workers beyond their cubicle walls. Your top people can raise the bar across the organization, provide strategic visioning, and fundamentally improve (which means “change”, a scary thing) how the organization functions.

Take an interest. IT pros work their butts off for people they respect, so you need to give them every reason to afford you some.

As said previously, knowledge workers will take bullets for those they respect. Once you’ve earned it stay engaged, take non-managerial interest in what’s going on, keep them excited about working for you even when the work they’re doing isn’t.

Favor technical competence and leadership skills.

When you notice a knowledge worker take the reins in a crisis and pull the whole group – possible even other groups – through it, that should leave an impression with you. That worker should be your right hand. If they aren’t in your team, maybe you need to figure out how to change that. When you notice a knowledge worker disavow responsibility for a failure – personal or team – or come up with lists of excuses, that too should leave an impression with you. Irresponsibility is not a trait of a knowledge worker. Not ever.

If you need someone to keep track of where projects are, file paperwork, produce reports and do customer relations, hire some assistants for a lot less money.

Delegating chores and administravia to knowledge workers is a waste of money, brainpower, and above all: Respect. Insulate your brainshare from these items and let them provide you value.

When it comes to performance checks, yearly reviews are worthless without a 360-degree assessment.

Everyone hates performance checks, whether knowledge worker, clock-fodder, runt or luddite. The key item is that knowledge workers are all for assessments if they’re purposeful and logical. Having a manager rate a subordinate (generally higher than they deserve), write some courteous crap (because their MBA professor told them that positive rewards work better than punishments) and give them goals to work on (because there’s always room for improvement), is an illogical, purposeless system that doesn’t result in the subordinate understanding any more about themselves or their performance. It’s total crap. Total. Crap.

Multi-factor assessments (such as the 360, the author mentions) are actually logical, have defined purpose, and result in a fairly consistent understanding about how their performance is perceived. MFAs involve diagnostics by superiors, subordinates, peers, and others with sufficient contact and experience: Sometimes major clients, organization psychologists, whomever. This takes a lot of work, but I’ve seen it correct some fairly chronic problems in short-order. Seeing that everyone thinks you need to shower more, generally has some impact.

Periodically, bring a few key IT brains to the boardroom to observe the problems of the organization at large, even about things outside of the IT world, if only to make use of their exquisitely refined BS detectors. A good IT pro is trained in how to accomplish work; their skills are not necessarily limited to computing. In fact, the best business decision-makers I know are IT people who aren’t even managers.

I, like a lot of knowledge workers, wear two hats: We’re an employee somewhere, and we’re consultants. As employees, often, we’re undervalued, underpaid, and our opinions don’t matter outside of niche topics. As consultants, often, we’re prized and paraded, CEOs and CIOs hang on our recommendations, technical staff cower knowing our every gesture will generate work for them, and when the sizable invoice arrives the payment clerks make sure it is turned around immediately.

It’s a surprisingly sharp dichotomy to live with, but those of us that do this understand it: As employees, we make hundreds (thousands, sometimes) of decisions a day, fifty weeks a year, the vast majority of them silently making things better from the shadows. As such, the organization doesn’t really value our individual decisions. As consultants, we make a handful of decisions, all of them pedantically documented and justified, and our clients revel in the certainty that their consultant just made some amazing decisions, and will put together working groups to implement them post-haste.

I had a consulting gig a few years ago where I quickly identified a knowledge worker who was pretty much a subject matter expert in what I was there to do. I separated him from the greater group and we had a discussion over lunch, where he eventually confided his frustration that I was there at all. I told him, essentially, what was in the previous paragraph, and said he should start making all of his decisions out loud while I was there. It would be obnoxious, abrupt, and I would end up getting sick of it – but it served the intended purpose: He knew what he was talking about, and was making congruent decisions to my own. They didn’t need to pay me $5k/day to do what their in-house SME could do for far less. That was the last time they called me in for that topic, and last I checked, the SME was a division head.

As a manager, you need to pull your knowledge workers out of their zones. You need to get their opinions on greater organizational issues. Not only will they respect you for it, but the successes they breed will be attributed to your foresight in engaging them.

A Nice Little Bow

Taking an honest interest in helping your IT group help you is probably the smartest business move an organization can make.

I sound like a broken record, but it all really comes down to this: Engage, listen, learn, support, encourage, repeat.

Unlike in many industries, the fight in most IT groups is in how to get things done, not how to avoid work. IT pros will self-organize, disrupt and subvert in the name of accomplishing work.

If you have subordinates unwilling to do new things, learn new things, or avoid work- they’re not knowledge workers, they’re there to collect a paycheck. Where you should see heated battles is over the details: Which technologies should be used to solve a problem? Which systems should be involved? How will it be pathed? Where will it have dependencies? How will it survive global thermonuclear war? Can it be prototyped? Can it be virtualized? Should it be virtualized? Synchronous or asynchronous? Threaded or processed? Static or dynamic? Database or flatfile? Which database? I feel a lot better just writing out all those things. That’s what matters.

Our most dynamic group has taken a “build it, and they will come” mentality for numerous services that eventually became focal-points for the organization. They go out of their way to do “unofficial” development work, subversively at times, knowing that in the end they were making good decisions, and providing valuable solutions. That’s what a real knowledge worker does, and that’s really all they care about.

Yet humans are congregational, fashionable beasts. Humans, in general, want to be where there are other humans- even virtually. They want to be a “part of something”. They want to be on Facebook or MySpace. They want an iPhone. They want a Gmail account. They want to be LinkedIn. They love fads and the feeling of faux exclusivity that they bring, like Twitter. They fight against distribution.

The Fallout of Centralization

When Gmail is offline for a few hours, it makes international news. Millions of people across the globe are without e-mail! Crisis! Panic! When Facebook “gets a virus”, it’s international news! Millions of people are at risk! Crisis! Panic! When Twitter gets knocked offline, it’s international news! Millions of people can’t tell each other what they’re eating! Crisis! Panic!

Why won’t they get their e-mail from a more local provider? Why won’t they get other services from a more local provider? Why do people by Macs? Why do people like malls? They fight against distributed designs, and try to pull things together. “One-stop shopping” to a network neophyte is all giggles and rainbows- To a network architect it’s “bad design”.

Internet history is littered with fads and centralized solutions that inevitably fail to retain attention after the Next Big Thing arrives: But distributed solutions tend to last much much longer. Why?

The Argument for Centralization

There’s only one reason Google loses more money than my lunch cost every time someone watches a YouTube video: Control. Companies offer centralized services so they can control their users, their content, and their market. Facebook doesn’t care about user privacy or quality services, they care about making money (or, in their case, losing less money). They want you to be on their site as often and for as long as possible, and they’ve already sold your information in order to fund more gizmos and whirligigs (”apps”, they call them) to keep you coming back and sticking around. Control.

If Facebook was distributed – anyone could put up their own Facebook-compatible site, and allow other geographically-similar people to use it – how would they exercise control? How would they censor you, collect your personal data and sell it? How would they push you the latest version of your favorite whirligig? How would they profit off of you (or prevent someone else from profiting off of you)? Control.

While Gmail is a centralized interface to a distributed system (collectively known as “e-mail”), they’d just love it if everyone used Gmail and there was no distributed e-mail system. They mine your e-mail for keywords to target ads at you, making truckloads of money at the expense of your privacy- Ads that companies pay a premium for because Google can already “guarantee” you’re interested. Control.

The Argument for Distribution

Keeping components small, simple, and “close” is a doctrine of many disciplines, and is imperative for “critical infrastructure”. I have more than one client that intentionally buy equipment from multiple vendors, to reduce risk of single-vendor product failures. Several only update a fraction of systems and application software to new versions at a time, to reduce risk of debilitating bugs (one client, literally, has some 8 year-old operating systems running unpatched for this reason). More, and more institutions have multiple WAN (”Internet”) connections, from multiple providers, to reduce risk of single-provider failures.

Distributed infrastructure is more about “us” (the global network users)  than “you” (the individual). You don’t care whether Gmail (with a few million users) is down, or whether your ISP (with a few thousand users) is down: all you care about is that you can’t get to your e-mail. Because of this, it’s hard to convince “you” that distributed is better. You, the individual, don’t care about network survivability or how many other people are impacted- you only care about yourself, and your inability to access your mail.

Would you like to travel to your State capital to go to a centralized hospital? How about to the National Library to check out a book? When it comes to travel-related logistics, most people go “duh, local hospitals and libraries and schools and whatnot make tons of sense”: But once they go online – once that facade of geography is lifted – eYouSpaceFaceGoogleTwitterBookMailBay.com really is the best thing in the world, OMG?!!

HOWTO

So what can we do? What can you do? Appreciate and utilize local, distributed infrastructure. Don’t outsource/offshore your new whizbang application when your local hosting provider can handle it. Limit your dependence on centralized services, and find distributed substitutes where needed. Pretty much every infrastructure application has a distributed counterpart, many of them with much much less evil than their centralized cousins. I’m not saying “don’t go to website X” – I enjoy Wikipedia and CNN and all sorts of centralized information sources – but I don’t depend on them for communication, and I certainly know other places to go if they’re offline.

Distributed service architectures are about freedom and survivability. Centralized service architectures are about captivity and control. Happy Birthday, Internet. I look forward to another 40 years of architectural ingenuity.

Where has this phrase gone? I’ve stopped saying it, subconsciously. I think it’s because everyone around me doesn’t say it. Then, for some not concious reason the other day, I said it and was scowled at. I found that interesting.

We are, it seems, obligated to minimize our efforts that people thank us for. Instead of saying “you’re welcome” we say “no problem” or “no big deal”: We go out of our way to make the other party feel like their thanks was nice, but unnecessary-that our expended life energy on their behalf was somehow forgiveable and not worthy of mention- instead of making it clear that their thanks was necessary, and yes we did do something that they should remember- our life energy was expended for them, and is forever lost.

The scowl was because I committed a modern faux paux: My expression of “you’re welcome” obligated the thanker to acknowledge- internally at least- that someone did do something for them, and it wasn’t just “no big deal” or “no problem”, and they resented that.

So it ends now. The responses of ‘np’ and ‘nbd’ will be replaced with what they should have been all along: “You’re welcome” (or ‘yw’) and I heartily encourage everyone else to do the same.

~2lbs sirloin tip
3-4 bacon slices
1/4 cup flour
1 tsp. ground sea salt
1/2 tsp. marjoram
1/2 tsp. thyme
1/2 tsp. ground pepper
2 large cloves garlic, minced well
1 beef bouillon cube, crushed, or 1 packet beef ramen flavoring
1 cup burgandy wine
wide egg noodles

In large iron skillet, cook bacon until well-crisped (brittle). Remove bacon to small plate. Roll beef tips in flour and brown on all sides in bacon grease. Break up reserve bacon into smallish pieces, and combine with beef and remaining ingredients (not noodles!) in slow cooker. Cook on low for 6-8 hours. Serve over cooked noodles, goes well with a side of steamed veggies and good loaf bread.

Serves 4. Prep time: ~20 minutes. Cook time 6-8 hours.

2-3lbs boneless chicken breast
1/2-1 cup red wine or burgandy
2 cups Dinosaur BBQ Slathering Sauce
3-4 assorted hot peppers, chopped into large pieces
1-2 large cloves garlic, chopped
large tortilla shells
1-2 cups sharp cheddar cheese, shredded
olives/lettuce/sour cream/etc. etc. as desired

Add chicken, wine, bbq sauce, peppers and garlic to a slow cooker and cook on low. It’ll be done in 4 hours, and can sit for up to 4 more hours and still be wonderful. If you’re averse to pepper heat, remove seeds and any yellow interior lining from peppers prior to adding them to the cooker.

When done, shred chicken with a couple forks in the cooker to help soak in more juice. Make wraps as desired.

Prep time 10 minutes (5 before cooking, 5 after). Cook time 4-8 hours.