Fifty2One
Legend in my own mind
- Local time
- Today, 05:21
- Joined
- Oct 31, 2006
- Messages
- 1,412
Ok my turn to rant.
I've been building web-based applications for this firm for a while now as a 3rd party contractor. They decide they need to employ someone in-house who who will do all the administrative stuff and help out on some coding (vb.net/c#). Fair enough.
So all the code is written in an n-tier structure where the business objects are seperated from the web pages blah blah blah. I spend the best part of three weeks explaining to the newcomer why we do this. "Yeah cool. I see that. That really makes sense" etc etc is the response.
So I've built a bunch of classes to abstract away from an xml news feed service. All the newcomer has to do is grab a typical class called article and load the webpage with it's properties. Well he's had previous .net experience hasn't he? So when his boss says can you create a list of articles each with a brief summary of the article text, he decides to go it alone.
First off he writes some code to trim the body text to a minimum number of characters. He doesn't check beforehand that the body text is at least the length of the string he's trying to trim down to. So with all short articles an error is thrown.
He then proceeds to NOT place this code in one place in the business object which I had told him about a thousand times to do but in every single webpage where the article is rendered. (It turned out to be 10 different places). He installs it on the live server and of course the news service sends down a short article through the feed and the site breaks.
I have to trawl through the site searching for all the copies of the crappy code and point it to a singular debugged function.
Don't get me wrong. Writing buggy code is human. But if someone has taken hours explaining to you how to do something you don't know how to do and then you proceed to just completely ignore them. Then I start to get aggravated.
Geeee DanCat if you and this other person team up and get a government or large coprorate contract the two of you could carry this tag team on until retirement age and then get on the consulting bandwagon.
But seriously if you keep hopping into the bail the bugger out mode then the person will never take ownership or responsibility for the messups created... let the employer get pissed enough and then save the day BEFORE they promote the newcomer for all YOUR hard work.
Last edited: