You must be experiencing a little bit of the 'butinsky' sydrome? :o) When someone sticks their nose into your business where it doesn't belong? :o) That is a common problem with co-workers in large corporations. It is one of the reasons I've always preferred to work in a small company (if the small company can provide good benefits).

Speaking of mico-managers, you expect that behavior when you are a new developer just getting your feet wet in the 'real world' because businesses cannot afford to let an inexperienced developer put code in a live product without supervision. That is typically the job of the lead or senior developer though as well as quality control (testing). I think the problem is more common when a developer makes it to corporate vp or a similar position though. They sometimes have a hard time letting go and letting people do their jobs when that job is the same job the manager did themselves for years.



>>Having suffered the consequences of a 'mico-manager' on numerous occasions, I'm jumping in here to clarify alittle.
>>
>>A micro-manager assigns a task to an individual or group of individuals (delegates). The manager then proceeds to tell the delegee exactly how to complete the task - sometimes step by step getting down into the nitty gritty of the task. In my opinion, there is nothing more frustrating, especially in programming. A programmer should be able to take a list of standards or guidelines and adhere to them. He/she doesn't need someone coming along and saying 'I prefer that we do it this way' on almost every block of code when the change does not improve readability, adhere to the standard, or speed up the processing. I have had managers change my code (and in some cases break it) because they preferred it to look another way. It's always fun to go back and fix the 'fix.' I had one manager that loved subroutines to an extradinary level. All programs were coded numerous levels deep. It drove me nuts when I had to trace code. Some procedures only had a couple of lines in
>>them before they called another procedure, etc until I had traced through so many levels I had a list a page long for a simple function.
>
>Thanks for putting my mind at ease... my case doesn't sound that bad now :).