Ha Ha! Now I can really throw the cat amongst the pigeons!I work for a business developing applications in a system called Pega Rules Process Commander. It's a BPM suite made by PegaSystems. I am not qualified in anything at all, but I'm a bit of a self taught geek who has occasionally dabbled in HTML and Java, but not to any real level that I would consider 'programming'. The combination of a logical brain, genuine business experience, the stamina to work through techy books to expand my knowledge and a system to work with that makes sense to me has led me to call myself a 'system architect'.
Having browsed the internets for information to further my knowledge of PRPC, I know that there is a growing level of hatred for people like me from traditional Java developers. I don't fully understand it, but they seem to struggle with the principles and simplicity of PRPC and seem to really resent its presence. They want to be able to suck air through their teeth like a mechanic about to make a big quote when they are presented with any development work. I just say 'give me some requirements and I'll let you know what I can do'. On the whole, I can have a proof of concept test model ready within a week for any new application or enhancement, and I normally end up expanding on the requirements themselves since I have the business knowledge to do this as well. On the whole, this POC model goes into production within a month, and so far I have not had any failures.
This is causing a bit of friction with all the old IT crowd. They want to go through endless 'high level' requirements that somebody being paid a lot of money can then turn into 'detailed requirements' that can then be passed onto somebody else for an impact assessment including costings, that can then go on to a steering committee for further approval before engaging the technology team who can then assign several developers to work on it whilst a change team produce reams of planning documentation before we enter 5 stages of testing, including largely unnecessary regression testing, and then after a year or two, the change might me implemented, unless the budget has been blown and the whole thing has been dropped.
Developers don't like me and my application, and understandably so. Last change I made to the main business application cost them less than 10k, but estimations from the traditional route put costs at a minimum of 150k!
This is not necessarily relevant, and I do understand the irritation with the whole SEO thing, but times move on, and systems and requirements change, and sometimes, it's better to bite the bullet and go with it.
One thing I completely agree with is the Social Media 'Expert' thing. I've never really 'got' twitter, and as far as I can see, facebook is all about making a fool of yourself after a heavy saturday night. Why is there a need for an 'expert', and why do people (the media) care?!?
(Having browsed the internets for information to further my knowledge of PRPC, I know that there is a growing level of hatred for people like me from traditional Java developers. I don't fully understand it, but they seem to struggle with the principles and simplicity of PRPC and seem to really resent its presence. They want to be able to suck air through their teeth like a mechanic about to make a big quote when they are presented with any development work. I just say 'give me some requirements and I'll let you know what I can do'. On the whole, I can have a proof of concept test model ready within a week for any new application or enhancement, and I normally end up expanding on the requirements themselves since I have the business knowledge to do this as well. On the whole, this POC model goes into production within a month, and so far I have not had any failures.
This is causing a bit of friction with all the old IT crowd. They want to go through endless 'high level' requirements that somebody being paid a lot of money can then turn into 'detailed requirements' that can then be passed onto somebody else for an impact assessment including costings, that can then go on to a steering committee for further approval before engaging the technology team who can then assign several developers to work on it whilst a change team produce reams of planning documentation before we enter 5 stages of testing, including largely unnecessary regression testing, and then after a year or two, the change might me implemented, unless the budget has been blown and the whole thing has been dropped.
Developers don't like me and my application, and understandably so. Last change I made to the main business application cost them less than 10k, but estimations from the traditional route put costs at a minimum of 150k!
This is not necessarily relevant, and I do understand the irritation with the whole SEO thing, but times move on, and systems and requirements change, and sometimes, it's better to bite the bullet and go with it.
One thing I completely agree with is the Social Media 'Expert' thing. I've never really 'got' twitter, and as far as I can see, facebook is all about making a fool of yourself after a heavy saturday night. Why is there a need for an 'expert', and why do people (the media) care?!?
more balanced than jeremy beadle It wasn't me...,
Tue 22 Jun 2010, 0:48,
archived)