Archive for December, 2008

It’s a Living

It’s the last day of the year and I am going to spend it doing something that on the surface sounds really stupid, and if you go a bit deeper, probably is.  But it is something that the rule oriented world in which I live has forced me to do. 

 

While many other offices are shut down  or at least closing early so that people can run home to open wine bottles and get their cocktail supplies in order, I am going to fly to Des Moines.  That in itself is not too stupid (what do you want me to say, someone from Iowa might read this).  Des Moines is a pleasant little town (whatever) and I used to have a client up in Ankeny.  Used to.  They were bought out by an even larger company that didn’t know me, they either moved or eliminated their IT group to Memphis, and they switched to a different software package for their ERP.  Somewhere in that process we just sort of drifted apart.  Stop me if you’ve heard this one before.   To this day they remain the one and only client who closed their plant due to weather (winter blizzard) while I was there.  Can’t remember if I charged them for the day or not.  I should have.  All the restaurants in the area closed and it was a very, very long day. 

 

Anyway, I’m not going to see them.  In fact I’m not going to see anyone.  No, I am just flying to Des Moines, getting off the airplane, walking around the gate area once or twice so I won’t look suspicious, then reboarding the plane and heading for home. 

 

Now I am sure that some of you have figured out what’s going on, maybe all of you.  You see, I am three segments short of reaching the Premier level with my flight carrier of choice and so, I picked out a day and a flight that was very cheap, and I am getting what I have coming to me. 

 

Never had to do this in the old days.  I was flying almost every week then.  But today many people are quite happy to have me work on their issues from home and so my actual trips have become few and far between.   The end result is that I finish the year short of the required number of segments to meet the Premier eligibility which makes it possible for me to get preferred seating in the Economy Plus section of the plane that features an additional 5 inches of space between myself and the seat in front of me. 

 

5 inches.  I know, it’s pathetic.  I am going to blow a whole day (actually two days, I was really seven segment short so I went to Des Moines about two weeks ago) just to get those 5 inches.  But to me it’s worth it and so, even though I have been a top tier flyer with this airline in the past, have flown them almost exclusively for the last dozen years, and am inching closer to my million mile mark, unless I have 30 segments by midnight tonight (today will give me 31) I will be stripped of my privileges and consigned to steerage, forced to sit beside and behind people who look like they are on some sort of work release or who are taking the whole clan to Houston to visit Aunt Patsy.  

 

And as I do this, I can’t help but wonder how many other things I do and how much time I waste fulfilling societies little equestrian jumps.  If I had $10,000 for every time I jump through somebody’s hoop would I be rich enough to tell them to shove it instead?  Maybe I’ll keep track this coming year.   After all, I’m ending 2008 with a totally ridiculous act, why not keep up the trend in 2009.

What Goes Around . . . Goes Around

Most of you are not going to be able to remember this, but for me it seems just like yesterday.  All of us in MIS would wait expectantly each week for Computer World to arrive, and we would dive into the want ads just to reassure ourselves that there were companies out there who would gladly hire us for double what we were currently making.  Yeah, we might have to relocate to Saudi Arabia, but who cares.  Just look at those salaries! 

 

There was one other thing that was part of just about every edition of Computer World (and every other IT magazine at that time); an article about the dangers of ‘islands of data’. 

 

You see the year was 1980 and every company in America was getting an IBM something or another, and either building their own MRP II system or else loading a package they had purchased.  And what was the reason for this unprecedented surge in activity?  It was the realization, sometime during the 70’s, that much of the data that actually ran these companies was in private hands.   Sales had their data.  Engineering had theirs.  Finance had a third set.  Companies looked like the Hawaiian Islands of the 18th century, little islands of data, each ruled by their own king and separated from each other by shark infested waters.  Islands of Data.  

 

This was long before PC’s, of course.  Most of the local data was held in card files.  In fact most departments had a big ‘tub’ file that carried the pricing or engineering data that was used on a daily basis.  The tub dated back to the 20’s and was defended by a guardian (usually someone who had been there since the 40’s) who spent all day looking up data and modifying what was on the cards.  The saying used to be ‘if you can still read the card for all the scribbling, then there’s not enough information on it yet’.   But times were changing.  I can still remember the lingering, pungent smell of tear gas as one by one the tub file redoubts were assaulted and taken by the IT shock troops, their data being carried off to the data entry group who would faithfully load it into the new MRP system. 

 

By the end of the decade, most companies felt they had made islands of data a thing of the past.  Their data was united, it was in the MRP system.  Everything had unfolded as IT had foreseen.  Victory was now complete. 

 

And so I was at a client the other day working on a system to track their buy item costs and how that impacted (or didn’t impact) their customer pricing.  In the process we realized that there were very few weights loaded in the Product Master File (which made it hard to calculate an extended material cost for various products at various prices per pound).  When we asked the engineers, all of who have been hired within the last two years, we found out that they kept the weight on a spreadsheet, they don’t load it into the Product Master.  In fact, much of the data they have on the product specifications is kept in spreadsheets, rather than in PRMS.  

 

Nor are they alone.  In the past ten years, everyone has gone spreadsheet crazy and in most companies today there is probably as much or more data on departmental spreadsheets than there is in the real business system.   And there is more data than that on company wide spreadsheets loaded out on the network, spreadsheets that while they may be visible to all users are still invisible to the ERP system.   This isn’t data that is ancillary either, it is mission critical data, being abstracted from the system or entered directly into spreadsheets where it can be changed without the benefit of the protection-ary editing of an ERP system.   In just about every company in America today, these data ‘files’, these ‘islands of data’ are becoming the defacto standard.  

 

What goes around . . . goes around, and around, and around. 

 

Now there are lots of things I don’t know, but one thing I do know is that data that doesn’t interact with the ERP system but which you use to make decisions, is not a good thing.  In fact, it is a very, very bad thing and if you disagree with that I sure as heckfire would like to know your reasoning. 

 

If it were up to me, folks who have this type of data would be singled out.  They could be fined and made to wear silly clothes.  Someone should walk before them crying out ‘Data Hoarder, Data Hoarder’ so that all might bear witness to their humiliation and shame.  Unfortunately, so far, it’s not up to me. 

 

But what really bothers me is I don’t know what will push us to consolidate these ‘islands’.   I mean nobody reads Computer World anymore.  And I’m not sure I can count on companies to do it on their own just because it’s a good idea.   Is it possible that things are really more out of control today than they were in 1981?   I suppose not, but I do know that the more decision data we have outside of the ERP system, the less real control we have over our enterprise. 

Agile Development and the ‘i’

You don’t hear as much about Agile development methodologies in the i world as you do on the web side.  It’s all the rage over there.  And I bet many ‘i’ people really don’t know what ‘agile’ is all about. 

 

Some people, like Mel Beckman, think it’s because of RPG.  In a June 1, 2008 blog post on the System i Network site (Boutique Languages), he gives a number of reasons for why agile is not really practical for the i world, and the inability of RPG to do this and that is the main culprit.  Now the main point of the post is to talk about some of the boutique languages that are emerging, and I’m cool with what he says about that, but I disagree pretty heartily about the RPG and agile comments. 

 

I think the reason we i people don’t do agile is much simpler.  I think it’s because we don’t design anymore.  We don’t have time.  Correction.  We don’t take time.  Got to get it done.  Management wants a function out there.  Generally it’s late even before you begin.  Get a general idea of where things are going and it will all work out in the end, and if you have to do a little tweaking (or even a complete rewrite), that won’t take too long.  What’s important is getting started right away. 

 

And because we don’t design, because we just dive right into things, we get off on the wrong foot.  We stop thinking about the problem we have to solve and how we can break it apart into stages and we start thinking in terms of code and how we can perform the mechanical steps.  And that kind of mind set has nothing to do with RPG but maybe everything to do with the difference between i and web programmers. 

 

Is it possible that web programmers, because of the visual nature of their environment, are more  interested in how the whole thing fits together than i programmers?   Maybe that’s an unfair way to put it.  Is it fairer to say that web programmers, because of the visual nature of their world, spend more time thinking about the finished product, while i programmers are more concerned with the nuts and bolts of what has to be done? 

 

Whatever the reason, agile is a very valid development methodology for the i world.  It has nothing to do with the language that is used.  It has everything to do with the way you approach a project, using a series of short interval iterations to help you and your user reach a full understanding of what the problem is and what the solution is going to be and how you will turn that solution into a reality.  Agile is a method whose time has come, whose time is actually past due, and it is a method that can fit well in the i environment. 

 

For more information on Agile Development and how you can use it in your shop, contact SCS (support@shireyllc.com).  Â