Blog For Free!
Archives
Home
2008 October
2008 September
2008 August
2008 July
2008 June
2008 May
2008 April
2008 March
2008 February
2008 January
2007 December
2007 November
2007 October
2007 September
2007 August
2007 July
2007 June
2007 May
2007 April
2007 March
2007 February
2007 January
2006 December
2006 November
2006 October
2006 September
2006 August
2006 July
2006 June
2006 May
2006 April
2006 March
2006 February
2006 January
2005 December
2005 November
2005 October
2005 September
2005 August
2005 July
2005 June
2005 May
2005 April
2005 March
2005 February
2005 January
2004 December
2004 November
2004 October
2004 September
2004 August
2004 July
2004 June
2004 May
2004 April
2004 March
2004 February
2004 January
2003 December
2003 November
My Links
My Photoblog
100 Things About me
My flickr stuff
Are you here?
tBlog
My Profile
Send tMail
My tFriends
My Images
Sponsored
Blog
| ++We have sheep here |
| 09.27.05 (6:29 am) [edit] |
|
Some of our programmers here are so apathetic. It's frustrating. It's also frustrating nobody is accountable for anything. I'm trying to document some new fields on a form. The name of it is "Debt Cancelled." The tool tip says "debit cancelled." I ask the programmer for clarification to make sure the tool tip isn't supposed to say debit. Instead of answering my questions, she directs me to the out-of-date design spec that I've already looked at (where else am I supposed to get my information? In a perfect world, I don't even have to go into to the code to figure out how it works. In fact, I shouldn't even have to.). She also tells me she was only following the design spec. :roll: Developers are allowed to develop as they see fit as long as it all works. IT'S OKAY TO FIX TYPOS, if that's what they are. So helpful, these people. I thought I'd make things easy by asking short and direct questions, but no. They tell me to go read a design document which "explains it all." And you know what licks even more? Programmers not taking the iniative to use consistency. If you're going to use the fields that do the same thing on different forms, for pete's sake, use the same names and spelling. We have these two fields called ytdintporn and usaytdintporn. I think they just wanted to use the word "porn" in our code. My appointment with my insurance claim adjustor went well. I'm going to see my doctor again, and then start physio treatments soon. Then after a few months, we'll settle my claim. What I am hoping for is an active rehabilition recommendation. Physio only helps me for so long. |
posted by: alliebar (reply)
post date: 09.27.05 (5:47 pm)
Sounds like we are in the same line of business. Many of my developers are sullen, and duck for cover when they see me coming. One technique I have found that works is to start out with a compliment (sincere or otherwise) like...I am told you are the expert on this and I was hoping you could give me a few minutes of your time to help me out with documentation......or other variations... As degrading as it sounds sometimes stroking egos works
Good luck!
posted by: rosietulips (reply)
post date: 09.27.05 (8:58 pm)
Reply to: alliebar
*L* Thanks. I'll have to try to stroke some egos next time. I feel so fake doing that kind of stuff, though!! Maybe I should be in people's faces more often. I tend to use email whenever I can.
www.flickr.com
This is a Flickr badge showing public photos from RosieTulips. Make your own badge here.