Skip to main content

Accomodating the Client

Working out how far to go to accomodate the client's needs.


Despite my talk about how I have "fired" the industrial client, I have been working with them over the past three weeks on certain issues that they are having with the VB 6/SQL Server systems I helped to build. This support has been for free. It is becoming the scenario that I didn't want to get into-- having to support their system because the project champions at the client don't have enough technical competence to support the users, and the IT department is unwilling to support the application because "something better" is coming along soon. Despite my desire to wriggle free from this client, I can't, after all, just throw them overboard; I don't see that as being the responsible thing to do. I have also committed to helping them with the application that interfaces with the tool controllers, but I have made it clear that that application needs to be written in C++, in order to accomplish what they want to do. It also serves my goal of being able to work with an application in C++, as a step away from VB 6-- the first step down what I hope will be a different path in my programming career.


I made a request that I be able to work from home, to minimize the amount of commuting I would need to do. The project champion at the client made my request known to the IT manager at the plant, and he said that it couldn't be done because of Sarbanes-Oxley issues. Which is interesting, considering that people at the staffing agency I work for tell me that other developers have worked from home for this client in the past. This could be interpreted as another attempt to squelch this situation and put up as many roadblocks as possible to using the software systems we have developed. To be fair, this client does have auditors who are following the practices of the plants pretty closely and tracking their compliance with Sarbanes-Oxley. But the only reason that they need these tool controllers and an application to track torque is because of an urgent safety issue that directly affects their customers. This is one situation where the "provinces" can't wait for IT to deliver a system.


I am not trying to take advantage of this client, and I am not trying to be difficult. My desire is to deliver an application that works well for them. My desire is also to build my skills for the future, and the tool controller app is a big opportunity to do just that. I am still wary of what kind of situation there will be when I return, even if I have a work space that is relatively free of distractions. One thing I am concerned about is how the project champion will pester me to tweak the other apps that are out there, and it is for this reason as much as the environment in the IT department that I would prefer to work at home.

Comments

Get any Desired College Degree, In less then 2 weeks.

Call this number now 24 hours a day 7 days a week (413) 208-3069

Get these Degrees NOW!!!

"BA", "BSc", "MA", "MSc", "MBA", "PHD",

Get everything within 2 weeks.
100% verifiable, this is a real deal

Act now you owe it to your future.

(413) 208-3069 call now 24 hours a day, 7 days a week.

Popular posts from this blog

Back to the Future

What can Lisp teach us about the future of programming? For a while, Slashdot was a favorite web hangout of mine, and I racked up probably close to 100 posts. My attention to that favored web site of geekdom was interrupted two years ago by my mother's illness and decline, as well as by my concentration on several dev projects that took up a lot of what had been my spare time. Now that I am off my last project and have a little time, I have been visiting with Slashdot again. A visit to the front page of Slashdot the other day is leading to an examination by me of-- of all things-- Lisp. The story that led up to this was a link to an article written by Simeon Simeonov, who, I believe, was the author of the Cold Fusion web scripting language. He discussed how he thought that "Rich Internet Applications" were the way of the future, and how "Composite applications"-- mixing HTML with server-side code and database access-- is not the right programming model, bu

The Never-ending Battle

Hints at market share for Windows and Linux. In the wake of the attack of the Zotob worm, I saw a chart from Netcraft that tracked the uptime of Fortune 100 web servers over the previous 24 hours. Apparently there was no effect from Zotob among the Fortune 100, as the server that had the most downtime was running Sun Solaris, and that might have been taken down for maintenance. Zotob seemed to cause more trouble on the intranets of several media companies, as CNN reported on Zotob as if it were some cyber-Armageddon. As it turned out, CNN's LAN just got hit especially hard. Looking over the Netcraft chart is enlightening. In addition to uptimes and other network-related statistics, the operating system of each site is also listed. The dominant OS in the Fortune 100 is not Windows, but... Solaris. Solaris runs on 42 sites, Windows Server runs on 25 of the sites, Linux on 17, another flavor of Unix runs 5 sites, and 10 sites have an "unknown" operating system. My gu