I'm on this new job for about three months. It's a .Net gig, mainly VB.Net (although I'm a engineering student with C++ background), but we usually write in whatever we wish, so, there's people writing in VB, others in C#, and the odd guy writing Access applications. I stick to VB.NET because that's what my boss asked for when I was hired.
It's okay, and quite fun at some times, but I've noticed that it's getting too close to Dilbert. I have lots of co-workers working on simple web pages for four months, while I get one week to learn SharePoint and redesign the new webpage (when I was supposed to be CODING), two days to learn the undocumented API of the management tool and make an online file transfer thing, finish other people's projects (meaning - write all the code based on a Visio document) on two days and present it to the upper management...
One of them could provide months of stories to this site. First, he doesn't know how to adjust his chair. Yep. He's supposed to code all day and doesn't even know why his chair is tilted towards him. We waited our boss to tell that to him because his too creepy. He also screwed up the production Web Server and spent four days trying to fix it. I would understand if we were talking about Linux, but it is IIS. He had 3 websites running on port 80, so, every time he clicked to start one of them, it would automagically stop the other two. So I came in and fixed the thing in about thirty seconds. Then he proceeded with whatever he was doing - he just said "I'm going to make a new folder for my project" and clicked on "New Website" again. I told him "You know you're not creating a new "folder", right? Use the Windows Explorer instead of the IIS Console.". Then he started screaming and telling how much I make people look stupid with all my cleverness, and how arrogant I was to think he didn't knew what he was doing... I just stopped talking and then he just started apologizing because he was working four days on fixing the webserver and stuff...
Two months later he wasn't finished yet. He wanted to input data on a ListBox and I told him to use the javascript "prompt" function, since he was taking waay too long. Then he decided my approach wasn't optimal and proceeded making a PopUp window that mirrored the look of the JavaScript one. He had all sorts of calls to the SQL server, a table that was used as temporary, and absolutely no concurrency guarantees. Two days later he wanted me to tell him how to hide "the X button" from Internet Explorer so "users don't close the window"......
Oh, and he was calling ASP.NET server functions using client javascript. For about a month he believed it worked, but the problem was with the database. Then I introduced him to the Internet Explorer status bar...
Later on, he also wanted me to help them with his homework. It was "mixed C/C++ stuff for converting integers into binaries and put the zeros/ones into strings". It had about 1000 lines of code, one class and used assembly calls and "CPU branching" (as he told me) to get each binary digit. Way too cool for him.
Fun thing is that there are lots of nice suprises. One of the my best friends here around here is a newbie and this is his first job on programming, but he makes great code... he keeps saying he doesn't know much, but he's great, actually.