aat liebert we always cross checked each others jsp, then graphics then its functionality on Live equipment, be it UPS, water detection or fire systems.
it was always a good thing to find mistakes in co-workers gode or design. good in the fact that we could get together and see how other developers would have handled the same problem diffrently. not in a "hey you suck" way. but in a hey check out this little line of code that can handle a temperature change of 4 degrees & compensate for the change befor we trigger an alarm & send 5 admins pagers, emails & phone calls automatically.. finding bugs was always fun! passing knowledge to co-workers was always a good way to stay in contact & Feel a bit livley. now if it is just ADMIN crap. just reporting some one sqrewing up, then i say fnck the man... unless it will get some one kilt, a server room melted or critical data lost... On 7/2/07, Heald, Timothy (NIH/CIT) [C] <[EMAIL PROTECTED]> wrote: > I was thinking the same thing. Communication between management and > worker must be pretty strained if you have that confrontational > attitude. Was it just the one person that was saying don't track the > issue, or does most of the team feel the same way? > > Watching out for each other is a good thing, until it becomes a bad > thing. As with anything it can be abused and make you look bad if the > individual in question continues to miss important things during the > development process. > > -- > Timothy J. Heald | NIH-Contractor | iGate > Enterprise Business Intelligence Branch (EBIB) > Division of Enterprise and Custom Applications, CIT/NIH/DHHS > Office: 301.594.5611 | Fax: 301.443.7010 | Email: [EMAIL PROTECTED] > > > > -----Original Message----- > > From: C. Hatton Humphrey [mailto:[EMAIL PROTECTED] > > Sent: Monday, July 02, 2007 1:43 PM > > To: CF-Community > > Subject: Re: Ethical question > > > > > Let's say a client called in cos something happened and you > > went ahead > > > and fixed the problem and it turns out that the cause was that a > > > co-worker missed out on some detail. Well I was about to > > write up a > > > ticket on it, without thinking, and another person said "No dont do > > > that we watch out for each other". And I nodded in > > agreement. So I didnt write it up. > > > > Did you at least let the co-worker that missed it know about > > the problem? > > > > The ticket system is (hopefully) in place to allow for > > feedback and positive growth. We all make mistakes, it's > > part of being human. > > Being able to identify our mistakes and correct them is part > > of what helps us improve as developers. That being said, a > > large number of tickets or problems reported can be an > > indication that someone is not learning from their mistakes. > > > > > And I also have an issue with the way things work here, cos > > it opens > > > up to people making easy mistakes. you know, stuff that > > should be automated. > > > > The truth is that there is a system in place where you work > > that people are purposely circumventing and that's nothing > > but bad news. I would suggest that you try to find out why > > it's happening and see what can be done about the source of > > the problem. It sounds like there is either a level of > > intimidation or miscommunication between you and management > > at this point, neither of which are good for production. > > > > HTH > > Hatton > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion MX7 and Flex 2 Build sales & marketing dashboard RIAâs for your business. Upgrade now http://www.adobe.com/products/coldfusion/flex2?sdid=RVJT Archive: http://www.houseoffusion.com/groups/CF-Community/message.cfm/messageid:237646 Subscription: http://www.houseoffusion.com/groups/CF-Community/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.5
