Being a blogging consultant is harder than being an unemployed blogger.
Last week I learned that only employees get to whine. Consultants get to bring solutions. Immediately. Without whining.
Chris--Stop reading--metaphors beyond this point will drive you crazy.
I met a developer consultant yesterday at work. We talked agile stuff. I haven't been working on any agile projects. It is so strange to go from software development to working in corporate IT. We think the blazing edge of technology is home, where everyone is doing tons of automation, and how you code on a whiteboard is what gets you the job, and everyone has hardware and software purchased THIS year and is using the newest Agile methodologies at least that the last 5 years has to offer. That is not true. Do you realize most of the corporate world is STILL using old operating systems? We are talking Windows XP with IE6.0 is the setup I'm testing for. That is the current use. Why? Because I'm not working at a technology company. They have real products that need selling! They aren't selling the bleeding edge. In fact, the bleeding edge could slice of a huge chunk of their business. The bleeding edge is a risk they don't need.
New things, such as planning training. Seeing just how willing to work around bad design they are if it helps the business. This isn't about doing what is ideal. It is about something that will work for their needs right now. I'm working on a product that was selected because it covered more of the features. There wasn't much talk about how it covered the features, just that it was already working in practice for other large business, and that it met more of the features for the price. This is how companies win projects. Because on time and on budget are what makes you "reliable" in business. Not just what you deliver.
As a consultant, I'm working safely on the handle of technology. It isn't the battering edge. It isn't any edge. It is the safe handle of the knife where the technology is second. It needs to deliver safely, without drama. No diva applications allowed. Here is where I'd break into the song, "A Whole New World" from the Disney Film Aladdin, but being that this isn't video, I'll refrain.
I am learning 2 scoops worth of new knowledge each day I'm at work. It is sort of like visiting another country for me, where I'm not sure I can live there, but I'm glad I came anyways, and I'd like to see all I can of real life while I'm there. Yep. Consulting. It is like taking a cruise (this ain't no backpacking tour), and trying to help as much as you can at each port, and leave it in happier shape than when you arrived. Now THAT would be a cruise worth taking.
Chris--Stop reading--metaphors beyond this point will drive you crazy.
I met a developer consultant yesterday at work. We talked agile stuff. I haven't been working on any agile projects. It is so strange to go from software development to working in corporate IT. We think the blazing edge of technology is home, where everyone is doing tons of automation, and how you code on a whiteboard is what gets you the job, and everyone has hardware and software purchased THIS year and is using the newest Agile methodologies at least that the last 5 years has to offer. That is not true. Do you realize most of the corporate world is STILL using old operating systems? We are talking Windows XP with IE6.0 is the setup I'm testing for. That is the current use. Why? Because I'm not working at a technology company. They have real products that need selling! They aren't selling the bleeding edge. In fact, the bleeding edge could slice of a huge chunk of their business. The bleeding edge is a risk they don't need.
New things, such as planning training. Seeing just how willing to work around bad design they are if it helps the business. This isn't about doing what is ideal. It is about something that will work for their needs right now. I'm working on a product that was selected because it covered more of the features. There wasn't much talk about how it covered the features, just that it was already working in practice for other large business, and that it met more of the features for the price. This is how companies win projects. Because on time and on budget are what makes you "reliable" in business. Not just what you deliver.
As a consultant, I'm working safely on the handle of technology. It isn't the battering edge. It isn't any edge. It is the safe handle of the knife where the technology is second. It needs to deliver safely, without drama. No diva applications allowed. Here is where I'd break into the song, "A Whole New World" from the Disney Film Aladdin, but being that this isn't video, I'll refrain.
I am learning 2 scoops worth of new knowledge each day I'm at work. It is sort of like visiting another country for me, where I'm not sure I can live there, but I'm glad I came anyways, and I'd like to see all I can of real life while I'm there. Yep. Consulting. It is like taking a cruise (this ain't no backpacking tour), and trying to help as much as you can at each port, and leave it in happier shape than when you arrived. Now THAT would be a cruise worth taking.
You definitely need to read "Crossing the Chasm" by Geoffery Moore (they have it at the Seattle library). He discusses the problem with high tech companies is they are staffed and usually geared toward early adopters and risk takers. Unfortunately the vast majority of people in charge of purchasing products are conservative pragmatists more concerned about support and wide adoption than features. Your statement about SB purchasing software because others had found it useful is textbook pragmatic purchasing.
Reply to this
This is one of my not well kept secrets, but I only read books that are fun in dead tree format. The only Python book I could use was Dive into Python because it was on the computer. I lose my mind (and make my pain worse) when going between book & screen. If there is an online format, I might be down with it!
It was really odd to wrap my head around this test plan because we aren't really testing the software, but instead testing the custom config and data transfer for business purposes! Whoa. Totally different.
Reply to this
Curtis is right here. I work for a firm that develops products for a wide variety of consumers, some of them government contracts, and while we try to keep as close to current as possible, it isn't always permitted in our technology refreshments. I think my computer still has Visual Studio 2005 on it (not 2008, or 2010).
Sometimes it may not be cost effective to be early adopters, but I've found its easy to fall behind the learning curve if you don't. If only Corporate level understood that.
Reply to this
I think one of the best perks in consulting is that you get to see how businesses make their technology work for their needs. More than just one company. Having spent 10+ years at Adobe, it is totally eye opening for me. I'm glad to have this chance.
Reply to this
Now, don't go telling Curtis he is right, since he's already going to get a swelled ego knowing he got me my current job! I sure owe him one. I should soon buy him dinner!
I'm an early adopter, but I forget that sometimes.
Reply to this
Congrats on your discovery of 'legacy' systems in the corporate world! I knew that would be a bit of eye-opener for you, and it's a consultant's realization that flexibility in the face of ambiguity, and being able to provide what's needed only when it's needed is an interesting challenge. Your audit capabilities are probably helpful, that is, being able to identify risks, inefficiencies, etc. But telling a client that their AS400 system is out-of-date and offering-up 21st century software solutions is often like asking for asking for someone's best squishy-face look. Better ...offer-up solutions for testing the current environment and work hard to define confusing or even non-existent requirements. Think in terms of use cases and what those ring-zero test cases are. Usability is the key and where you'll get your accolades.
Big change from Adobe for sure, eh! (
Remember, if asked to sit and have some coffee--always stay for what customarily comes next. Stay for the pie, Ed! (Erin Brockovich reference).
Reply to this
I wish you could have seen my expression some of the shocks the first few weeks. It is pretty funny. I am so lucky that I adore my test manager over at Sb. He is a cool cat. I can't wait to start testing. I want him to know what I can do!
Reply to this
Even high tech companies can suffer from legacy systems. The employer I work for does some amazing data analysis software for their customers, but it was to work on Solaris 8. The developers (and testers) always groan when a bug comes up that can only be reproduced on the legacy systems.
Reply to this
Companies have so much invested into the legacy systems that at time it costs a fortune and is a huge risk to migrate the data. I can't confirm or deny if some companies might wait so long they have to buy hardware that isn't even supported?
Reply to this
Hop in my way back machine to 2001, it's IE 6! This seems to happen everywhere in corporations. The only time I've ever seen anyone really push for a new version is when a major security flaw is found (Zero-day hack, anyone?). In my opinion agile has not help resolve this problem. Most teams are focused on delivering valuable software to their customers quickly and little value is seen by the customer to justify upgrading existing systems. If you want an upgrade, I recommend my request model:
Upgrading will save you X dollars
or my other favorite
Not upgrading will cost you X dollars
I enjoyed the Bach reference. “TWO SCOOPS! And damn the consequences.”
Reply to this
Gotta' love that! We have the same resistence to upgrade when we do Windows ACF (Application Compatibility Factory) engagements. Since ACF is a toolkit that Microsoft created to identify, inventory and remediate 'legacy' enterprise applications to run and play nice with Vista and Win7 security "upgrades" ...we see things like hundreds of little 'boutique' applications written in VB 6 and the like. So the resistance to even thinking about upgrading to Win 7 (forget about Vista!) and the lovely UAC is pretty intense.
Microsoft pays us to go-into companies and train a company's IT to use ACF, so it's no cost to them except their time. But even still, it can be pretty daunting when we first come-up with an application inventory of apps needing remediation. In some cases, companies will start to back-off on the effort thinking of how many things could break even after the ACF toolset has been applied. So when they start to back-peddle and cite the costs of app remediation we usually remind them of the those costs associated with 'not' doing anything.
Guess which is ALWAYS bigger?!
You're right.(
Reply to this