If a knowledgeable trainer is not available, and the training material does not "stand on it's own" - it might as well not exist. This article covers ideas on improving the state of your art. (Part of a series)
A rather rigorous, Financial-sounding title for a high-concept line of thought ... Thanks to Jeff Atwood at Coding Horror, for calling my attention to this article by Martin Fowler on Technical Debt: Technical Debt is a wonderful metaphor developed by Ward Cunningham to help us think about this problem. In this metaphor, doing things the quick and dirty way sets us up with a technical debt, which is similar to a financial debt. Like a financial debt, the technical debt incurs…
Got a simple request from one of the folks in Operations; we're sending out Excel spreadsheets for some quick data gathering, might we do a little basic input validation before they send in garbage that needs to be scrubbed? This person is very sharp, knows a decent bit about what is possible, and this is definitely not something that is worth a major project engagement; "throwaway technology", a particular fave of mine. His request was simple - just want to…
The start of a new year gives me a rare chance to measure my knowledge capture output over time. I maintain electronic journals for the various projects I am driving, business units and functional areas I support, and people I work with. This results in a hundred or so separate MS Word documents, with generally the same format - still, it would be quite tedious to take a word count each week to check my output. However, at the beginning…
It's been a while since I've led a requirements session for an interactive application - but no worries, I found it's like riding a bike. After a few minutes the old habits come back, and iterative ideas and cascading creativity starts to flow. What has changed, however, is the application platform, the office environment, and the various knowledge capture tools at our disposal. So, in the spirit of knowledge retention and sharing, here's a brain dump of ideas that I…
Last time, I wrote about checklists, and showed the example of the B-17 preflight. Simple, fits on a single page, and hits all the critical steps, in just the right amount of detail. Plenty of processes in the IT department are made That Much Better if they are accompanied by detailed, effective Process Documentation. Of course, that's all motherhood and apple pie - everyone agrees that the existing checklists are great. But how do you get started? I mean, assuming…
Why I think that every techie should go through the experience of building up a desktop workstation from the ground level. Maybe it's because I date back to the days of the PC XT, when computer support duties regularly had us tearing down cases, changing jumper settings and plugging in individual chips for memory expansions. Mainstream p0wnership of the desktop's guts may also be a dying art form (notwithstanding) - in the days of ubiquitous WiFi, shrinking notebooks, Blackberries and…
When talking about "innovation" in a non-digital firm, don't force-fit the trendy stuff - focus on the innovative stuff you've done with your traditional environment, like ERP and Data Analytics. Tie this to what creates value for the enterprise, and you have something meaningful.
I got a call a few weeks ago that put me in a slightly cranky, slightly bemused mood. This is not a recent phenomenon - it has happened at every company in my career. A few of the big-name vendors (including IBM, Oracle, SAP, Microsoft, HP, and others) have no problem peppering different people in a company with requests for basic information (What systems are your running? Do you have a general ledger system? Do you use computers? Do you…
As I've noted in the past, it really helps to understand the techies' way of thinking, especially when trying to get work done on tasks that are decidedly non-technical. Here's two more recent stories from work, both hinging on the common desire to just "git'er done". Why do we waste time removing obsolete code? Just hide the menu option ... A few months ago, we had a task to decommission a chunk of code that was calculating some elapsed time information…