Don't you hate it when ...
-
you come up with most of the important ideas for a new project, write all the code, demo to the analysts, users, and managers, and then just before release, some guy jumps in to criticize almost everything you did? He even sounds like he has been thinking about this for a long time and has a lot of much better ideas (just don't ask him to do any real work). I am so tired (and sick).[
My articles and software tools
-
you come up with most of the important ideas for a new project, write all the code, demo to the analysts, users, and managers, and then just before release, some guy jumps in to criticize almost everything you did? He even sounds like he has been thinking about this for a long time and has a lot of much better ideas (just don't ask him to do any real work). I am so tired (and sick).[
My articles and software tools
I feel your pain man!! ---------------------------------------------- If you need a hammer get C and shut up. If you need a nail gun get C++ and shut up. If you don't need *those* things (and good design should tell you) then by all means get a factory, factory, factory. --code-frog@codeproject
-
you come up with most of the important ideas for a new project, write all the code, demo to the analysts, users, and managers, and then just before release, some guy jumps in to criticize almost everything you did? He even sounds like he has been thinking about this for a long time and has a lot of much better ideas (just don't ask him to do any real work). I am so tired (and sick).[
My articles and software tools
You need to have thought about every criticism he has. If you havent, you didnt think enough about the design. Welcome this as a chance to show off your depth of consideration of issues infront of everyone else. For example, say to him 'I am glad you thought of that, it took me some time to work out a way of handling that situation' or some such. He will feel usefull, you will look clever, and the customer and manager will think they have a rock solid product. Nunc est bibendum
-
you come up with most of the important ideas for a new project, write all the code, demo to the analysts, users, and managers, and then just before release, some guy jumps in to criticize almost everything you did? He even sounds like he has been thinking about this for a long time and has a lot of much better ideas (just don't ask him to do any real work). I am so tired (and sick).[
My articles and software tools
-
you come up with most of the important ideas for a new project, write all the code, demo to the analysts, users, and managers, and then just before release, some guy jumps in to criticize almost everything you did? He even sounds like he has been thinking about this for a long time and has a lot of much better ideas (just don't ask him to do any real work). I am so tired (and sick).[
My articles and software tools
When it happen I usually kill him and hide the corpse under his own desk. :-D BTW, it happened just a few days ago. I designed a web page in a way I thought was good. The boss came and told me to modify almost all. I did it. Then a "associate" of us came, and told me the work wasn't that good because an unexpert user cannot understand what to do. I pointed out that the web application was not for "masses", but only for experienced users. He kept his position. And I kept mine. The web page has not been changed! Victory! :cool: ___________________________________ Tozzi is right: Gaia is getting rid of us. My Blog [ITA]
-
That the worst time you can have as a developer, :sigh:. It often happens to me. I get totally pissed off. I feel like saying simply a f*ck off.:mad:. X|
--[V]--
I tend to save it up. There's usually someone who acts like they know everything just a little better than everyone else. But at some point they'll slip up, and that's where you jump in to correct them. Makes you feel big, them feel stupid, and the world is put back to order.
-
When it happen I usually kill him and hide the corpse under his own desk. :-D BTW, it happened just a few days ago. I designed a web page in a way I thought was good. The boss came and told me to modify almost all. I did it. Then a "associate" of us came, and told me the work wasn't that good because an unexpert user cannot understand what to do. I pointed out that the web application was not for "masses", but only for experienced users. He kept his position. And I kept mine. The web page has not been changed! Victory! :cool: ___________________________________ Tozzi is right: Gaia is getting rid of us. My Blog [ITA]
-
No. Anyway I should move it... maybe this night. :doh: ___________________________________ Tozzi is right: Gaia is getting rid of us. My Blog [ITA]
-
When it happen I usually kill him and hide the corpse under his own desk. :-D BTW, it happened just a few days ago. I designed a web page in a way I thought was good. The boss came and told me to modify almost all. I did it. Then a "associate" of us came, and told me the work wasn't that good because an unexpert user cannot understand what to do. I pointed out that the web application was not for "masses", but only for experienced users. He kept his position. And I kept mine. The web page has not been changed! Victory! :cool: ___________________________________ Tozzi is right: Gaia is getting rid of us. My Blog [ITA]
-
I tend to save it up. There's usually someone who acts like they know everything just a little better than everyone else. But at some point they'll slip up, and that's where you jump in to correct them. Makes you feel big, them feel stupid, and the world is put back to order.
-
you come up with most of the important ideas for a new project, write all the code, demo to the analysts, users, and managers, and then just before release, some guy jumps in to criticize almost everything you did? He even sounds like he has been thinking about this for a long time and has a lot of much better ideas (just don't ask him to do any real work). I am so tired (and sick).[
My articles and software tools
Unfortunately, this happens much too often. It seems like these people [the ones that don't do any real work and criticize everyone who does] wait until the very last moment [after the coding is complete and you have invested time into getting things working] to inform you that they have problems with the design. There is usually much too much detail in their criticism for it to be a last minute thought. The solution to this is the tedious process of getting everyone's "buy in" in the design stages. That is call many design review meetings with follow up email to everyone involved summarizing what was agreed to at the meetings. Then if any objections to the design come up you can ask why this wasn't brought up at the design review. It doesn't solve the underlying problem but it at least points out that you tried to get input from everyone before you went to implement the design and shifts some of the responsibility back on the person objecting to the design. I'm on-line therefore I am. JimmyRopes