If I've been asked once I've been asked a thousand times; "how long will it take to create / convert / build / etc... ?" So, how do you answer this question? For example each report request is like a custom implementation of a one-off design. Sure, a report request is rather limited by what a user is asking for. Sometimes it is a request that the user wants some information based on how some other information is reported. For example; "I'd like a report that looks like the Marketing and Sales Report, telling me how many inquiries my reps are answering per hour.? Sounds simple enough; basically locate the source of the data, do some simple math and use the template (or the Marketing and Sales Report as a template) to build the report. Ultimately you'll be asked "so, when do you think I'll have it?" What they want to hear is probably expressed in minutes or hours. And some tools and frameworks can make this happen ( BIRT Report Studio ) but yo...

So, I'm logging out to catch a flight. Code freeze is tomorrow, and code release is scheduled for next week. Why then, do some users wait until NOW to tell me about corrections and tweaks to reports? -- (...yes, a couple... even I am not perfect!) -- My answer; they just don't care until they're reminded of the code freeze and impending release. Procrastination at its finest! It's a good thing I am using something as flexible and easy to modify as the BIRT Reporting Application. Changing things like column header names, some data type formatting, even script logic on various report elements is not a big deal (most of the time). This reminds me, that it is always a good thing to take the responsibility as a developer, to create a 'sign-off' check list. Trouble is, I HATE lists! But worse than that, I REALLY HATE being late to the Airport! I think I'll create a check-list and post it here (later)... why not procrastinate? everyone else does!

In Canada again! Longterm assignments are good, but they do have their drawbacks. First and possibly the biggest drawback is the "boredom factor". Secondly, it seems to me (possibly related to boredom factor), they longer I go, the longer the weeks seem to get. Now that I have gotten that off my chest, this is not a bad assignment at all. I most certainly have had worse. The best assignments are usually a blend of three things; 1-Location, 2-interesting / cool people, and 3-technology of interest. There is nothing worse than being on an assignment where you can't stand the location, if for no other reason than the office is just plain crappy. But, even in a nice location, with very cool geographic and environmental surroundings if the people suck, the job sucks. And finally if the first two items on the list are okay, I can live with the technology being boring or sucky... at least for a little while.

Often I find myself struggling with "where to start" issues. The simple answer is: 1- my own experiences 2- JFGI 3- groups and forums The problem is that my experiences are extreemly difficult to sort out as I am becoming older and am collecting more experiences. JFGI will only take me so far, eventually I need to apply a real answer and there is rarely a "perfect fit". and finally by the time I am looking through forums, I am just about at the end of my rope. So, where can I go from here? I find that networking with "real-people" is probably my best next place to build on. The problem is that this industry seems to be non-people related, in other words people who tend to go into IT are not very people-oriented. With the industry becoming seasoned and older, and the down-turn in overall markets one would think this will be something soon to be overcome. Lets see...

So, when it comes to building a reporting solution why is it that users just want to "Automate" their already overly complex and convoluted Excel or Power Points? Almost every engagement requiring a "Report" seems to start out the same way. There are two primary trains of thought, the first is to "Get Everything" and the second is to "Automate Everything". Business Analyst say they want "everything" when they don't know exactly what a "Reporting Application" is or they don't know exactly what they want in a Report or Report Application. It's kind of like the General Contractor, who'll tell you he does "anything" when you contact him/her to build you a Deck or replace your Roof. Anytime I see ambiguity at this level, I question the understanding level of the individual making the claim or request. There are two tactics I find very helpful when faced with a request that seems to be less than well though...

So, it's Saturday... Why am I still thinking about work? Disconnecting is probably the second biggest challenge behind Keeping Up. If I'm working on one, I am not working on the other. In effect, disconnecting is one of the attributes of "Keeping Up". Just like sleep rejuvinates the mind from a day of stimulation, disconnecting gives you time to rejuvinate your professional mind. Remember the addage "... All work and no play..." So disconnect today, it'll help you keep up in the long run.

So, one of the many challenges in this thing called consulting is "Keeping Up". Or at least this is the case from my point of view. "Keeping Up" encompasses so many different aspects; Keeping up with new trends, Keeping up with best practices, Keeping up with schedules, Keeping up with clients, generally keeping UP when everything is working to keep you down. It has been my experience that it is best in all of these cases to keep up by slowing down. This might seem a bit counter intuitive, but it can work. By slowing down I don't mean to become complacent and lazy, I mean to achieve heightened awareness through clearing and centralizing. Clear the clutter, and you'll be able to find things with greater efficiency. Having a clear spot or two on your calendar will open the door to introspection and recovery. Clear your mind of the excessive "noise" so the important things can be heard and seen. ...You get the idea, in other words Relax and Receive. W...