I don't remember a whole lot from the class on Systems Administration that I needed for my degree. Mainly because it was a matter of rote memorization, and that semester was pretty programming-intensive. But one of the few things that pops into mind from a decade ago is the set of options and trade-offs involved for cutting over from one software system to its replacement.
Option 1: Parallel systems transition Both systems are fully operational during the cutover time. The good: Output from the new system can be validated against the old one. Plus, if the new system isn't working as planned, it's simply switched off until the bugs can be worked out. The bad: Something like double the work (i.e. expense) will be involved, not to mention a certain amount of organizational disruption while things are sort of in wait-and-see limbo.
Option 2: Cold turkey cut-over You switch off the old system and switch on the new. The good: No double-expenditures, and the sheer act of cutting over is its own incentive to make things work. The bad: Not for the faint of heart, because if the new system is not working as designed, firing up the old one and bringing it back up to speed with the new data is pretty much guaranteed pain.
Seem pretty simple, don't they: The trade-offs between cost and peace-of-mind? But it boggles my mind to see how many people--even those who should know better--think they can have Option 1's safety-net for the price of Option 2. It just doesn't work that way, and I can confidently tell you that anyone who says otherwise is either a naif or a liar. Don't fall for it. Whichever cut-over option you choose, decide up front how much pain you and the organization can handle. Budget (time as well as money) for hiccups and for pete's sake make sure folks know the backup plan (you do have a backup plan?) well ahead of time.
This is probably old news to the veteran of even a single rollout. (Although I've noticed that cut-overs are like child-birth for some people in that you forget how gut-busting it can be until the next time around.) But for anyone who hasn't ridden that roller-coaster...don't say you weren't warned.
Thoughts on computers, companies, and the equally puzzling humans who interact with them
Wednesday, November 11, 2009
Minimizing the bleeding from a cutover
Tuesday, November 10, 2009
Something I hope you'll see (if you haven't already)
It's tantamount to moving away from home, knowing that a younger sibling will be moving her/his boxes into "your" room (or part of a room) the minute the last of your boxes is loaded into the car. It's incredibly scary, and incredibly exhilarating. Not something that happens often in the life-span of an organization, so it's exciting as all get-out to witness.
Monday, November 9, 2009
Deciding to decide well
I normally distrust simple prescriptions, which is why browsing the business section at the bookstore is particularly painful. But I've been turning the above idea over in my head since late afternoon, and still can't think of a single counter-example. Whereas the examples of friction are legion (although I tend to think of them as falling into basic categories):
- Bottlenecks (for which I largely blame the Cult of the CEO) due to tactical decisions being doled at the strategic level.
- At the other end of the spectrum, the Cult of Consensus, in which the organization hemorrhages productivity in meetings specifically designed to postpone decision-making (and spread the blame for any consequences of decisions that manage to slip through).
- Or (my personal favorite) the proverbial "re-arranging the deck chairs on the Titantic" schtick that likewise bleeds productivity with the bonus of allowing the slackers and martinets to contribute even less than normal, while sapping the morale of those responsible for getting work out under deadline.
Sunday, November 8, 2009
Another private eye who works for free
Well, "internet free," anyway.
This is more or less a follow-on to yesterday. If you're looking to scope out a potential customer/employer/competitor and the company is publicly traded, you can consider your tax dollars well spent in the SEC's second-generation "Oscar" tool. The link for viewing "Insider Transactions" is particularly useful as a "Who's Who" for both inside the company as well as who's pulling the strings from the outside.
Anyhoo, the base link for searches is here: http://www.sec.gov/edgar/searchedgar/companysearch.html. Booyah for transparency.
Saturday, November 7, 2009
WHOIS: Private Eye
But I kind of took a step back at this sentence in the reminder:
When renewing your domain(s), consider this: Did you know that you can increase your Search Engine Rankings by registering your domain name for 5 or more years at a time? Although a 5 year registration may seem excessive, search engines such as Google and Alexa appreciate and heavily weigh the longevity and stability of websites. Extending the length of your domain registration will help improve your search engine rank and to allow others to find you more easily!Now, I haven't bothered to corroborate the SEO claim, but it tripped the switch for a small light bulb in my brain. A case could definitely be made for using the WHOIS record for the company's web domain(s) (e.g. acme.com) for trying to get a better sense of a company. Maybe you're about to do business with it; maybe you just want to. Maybe you're a competitor or are trying to become one. Maybe you have a job interview with it. In any case, domain information is just another tool in your belt. Given that much of the information is "free," I think you'd be a fool not to take advantage of it.
It may be a matter of chance in timing, but if the renewal date's waaaay out there, you can make an intelligent guess as to whether the company prefers to invest up front to save money in the long run, or whether it prefers to live in the present. Did the company register the domain under its own name? Or did it register it anonymously? Or was the name registered by a third party, most likely the web designers?
If you have any sense of the various domain registration companies (a.k.a. registrars), it can also help fill in some of the pieces. Is registrar fly-by-night? Or a venus flytrap for the un-savvy? Bargain basement or boutique? Similar questions apply to the company that actually hosts the company's website, with the additional possibility that the company owns the server that hosts the website, which says something else entirely.
If you use a thorough tool like http://whois.domaintools.com (the free version of which rawks, by the bye), you can find out other interesting things about the history of the domain. Has it jumped around or stayed in one place? If the information's worth your coin, you can also find out where and when those changes happened.
Of course, if you're primarily interested in aspects of the company that don't have anything to do with their web strategy, the above will likely be a complete waste of time. But for anyone else, it's a peep through the keyhole at where I/T (particularly the webby bits) fit into their vision of the company. For me, that's very valuable information.
Friday, November 6, 2009
Frivolous Friday, 11.06.2009: Freaky Factoids
Prior to Halloween, I'd been hoping that the Weird Wisconsin website would return after being boarded up since sometime in 2007. Mostly because I've been a sucker for quote-unquote "true" ghost stories since grade school. (This despite certain..."incidents," such as the cat extruding herself from her hiding-place right next to where I was engrossed in a book of such stories. D'oh!). In addition to hauntings and other "unexplained" phenomena, Weird Wisconsin also featured the bizarre side of the state's history, in keeping with their motto: "When you go looking for the weird, the weird comes looking for you."
For instance: In 1912, Teddy Roosevelt was on campaign stop in Milwaukee while running for President under the Bull Moose (Progressive) Party ticket when he was shot to "avenge" the 1901 assassination of President William McKinley. The would-be assassin of (McKinley's) then-Vice President Roosevelt believed that the McKinley's ghost had asked him to settle the score.
Roosevelt went down from the shot, and the surrounding crowd tackled the shooter (John Shrank). Then Roosevelt--always larger than life--jumped up, shouting, "Don't hurt the poor man!" Although the bullet had entered his chest (where it was later deemed too dangerously lodged to remove), its force had been blunted by Roosevelt's eyeglass case and the fifty page text of the speech he was about to deliver. And deliver it he did, judging that because he was not coughing blood, the bullet could not have entered the lung. Only after his 90-minute spiel was he admitted to the hospital, where he greatly annoyed his neighbors with his snores.
But shuttered website aside, there's still plenty of weird...or at least lots of stuff that challenges our modern sensibilities and what we think we know about the past lurking in just about every nook of history. In this case, I'm reading Nancy Unger's Fighting Bob LaFollette, and thought I'd share some of the nuggets I've found, merely 1/3 of the way in:
- Bob LaFollette's paternal grandparents were neighbors of Abraham Lincoln's Mom and Dad.
- In 1875, the University of Wisconsin boasted 345 students, and the number of four-year university students in the United States was 27,000.
- However, even in 1875, the UW was co-ed: LaFollette met his wife as a fellow student.
- In 1860, the year the Civil War began, Wisconsin's African Americans could own property, attend public schools, sit on juries, and marry white spouses. However, the popular referendum denied them the right to vote, which was ultimately given by fiat of the Wisconsin State Supreme Court a year after the close of the Civil War.
- Cranberries were at one time an experimental crop, intended to diversify agricultural output in the wake of war shortages and crop failures.
- Ditto for hops, which contributed to the hundreds of breweries that made up Milwaukee's leading industry (in the 1870s or so)...and a 30% spike in Wisconsin's overall alcohol consumption. (And Oktoberfest begins!)
- In LaFollette's childhood, Wisconsin's sheep population outnumber its cows. However, by the time he was elected to the U.S. House of Representatives, Wisconsin was sufficiently "the dairy state" for for the frosh Congresscritter to attempt to protect its interests by arguing for a tax on margarine.
- Railroad titans were the Wall Street bankers of LaFollette's youth and early career, most notably for helping themselves to public land, and for fixing prices to the detriment of farmers and the cities that relied on their produce.
- (And speaking of corruption...) The safeguards against politicians abusing their powers were pretty much nonexistent. For instance: Philetus Sawyer, lumber baron and the senior Senator from Wisconsin during LaFollette's first term, ran through a law to sell himself timberlands belonging to the Menominee tribe. And it was considered routine business by all but the reformers.
Apart from the chance to collect oddball trivia ('cuz my brain is like flypaper for that stuff), I like to think that going on "weirdness safari" (particularly in history) is an excellent stretch for the brain. It counter-acts the too-easily and spuriously-used rationalization of "that's the way it's always been." I can't recommend the experience highly enough.
But for pete's sake, just make sure you know where the cat is.
Thursday, November 5, 2009
A few thoughts on digital tree-houses
The concept of online communities" is by now definitely mainstream, which hopefully means that the hype will finally die off soon. More hopefully, it's because the metric of "How much does this group accomplish in the real world?" will be more rigorously applied. Sure, folks like Guy Kawasaki can snort at people with few followers/tweets when they unfollow him for his redundant posting of the same link. Personally, I would rather withhold judgment until I see how gelled that person and their contacts are and what they do with that network of relationships. (And even then, I certainly wouldn't snort.)
As an example of what I mean by "gelled," the guy who owns Orange Computer in La Crosse--I didn't think to ask permission to name names, so you'll just have to check out http://orangecomputerlax.com for that--is hosting a Linux (Ubuntu 9.10) installation-fest this weekend. He's already following and being followed by several "techie" types in the area, so Twitter makes a natural medium for getting the word out. If the online and offline worlds of @OrangeComputer didn't overlap, the installation shout-out would be a complete waste of 140 characters.
It doesn't just apply to social media. For instance, folks with a number of skill-sets (programming, testing, documenting, building, etc.) can all roll the next iteration of Linux without ever meeting each other (much less Linus Torvalds) in the physical world. But they all have the secret password that allows them into the tree-house, because of their contribution to the software that ultimately powers real-world hardware for the real-world benefit of people and organizations.
The dot-com crash again tied the viability of a business to (gasp!) actual profits, rather than eyeballs or its prospects of being flipped to Yahoo!, Microsoft, whatever. Similarly, the more egregious abuses of Facebook, Twitter, etc. for spamming, virus-propagation, time-wasting inanity, and superficial "networking" will--I believe--place a greater emphasis on the offline value of an online community.
But there's the rub: How is that value quantified? How do you put a dollar figure to the amount (or lack) of trust that the members of a network have their alpha, betas, or each other? If I had a crystal-clear set of answers to those questions, I'd probably already be a millionaire with a viable shot at billionaire-hood. But I think one possible metric is this: How much is the community interested in their own numbers? Because a focus on the numbers is, in my opinion, an indication that there's no substantive vision there. In essence, the message being communicated to the outside world (i.e., would-be members) is the Web 2.0 equivalent of a chain letter.
Which, IMO, should be mere common sense. But every time I see someone swaggering online purely on the strength of her/his avatar-collection, I just cringe. Bottom line: Could you trust each and every one of your peeps to water the plants and feed the cats while you're on vacation? Do you even know them well enough to know whether or not you could make that kind of judgment in the first place? Because if you can't, you're basically expecting to pay the bills with Monopoly money. And we all know how well that worked out for Web 1.0...