Too Many Languages!

I recently started working for a medium company, after programming as a hobby or homework for over six years.
We're just two programmers in this company, so I end up doing web applications, desktop applications, front-ends, back-ends, APIs, design databases, and even give ideas to designers and others!
In this company they have things programmed in many languages for some reason, and I end up doing html, javascript, css, asp, php, c#, and more!
And I love it! Because I love programming but I get fed up with just one type of work very quickly, so if I have been doing something too technical, I can switch to javascript and have fun doing the eye-candy with nice ajax and scriptaculous, messing around with the html and css, and then design some database tables, and then do more back-end web programming, and then make a desktop application, and whatever!
I'm really given a lot of freedom, but I wonder, are all coders' jobs like that? Since this is my first job, I really have no idea. As a freelancer, I always did whatever I wanted to, too.
redpanda redpanda
18-21, M
4 Responses Aug 6, 2010

In my shop, we have two main categories of software/programmers: Java and .Net. The bulk of the work is in Java, so the Java developers do a lot of the ja<x>vasc<x>ript/Ajax and backend programming. I think we're down to one .Net developer (maybe two), understandably so since .Net makes up such a very small part of our software. <br />
<br />
I'm not counting languages like HTML, CSS, SQL, etc. in these categories, because from what I've seen, these are things most developers have to deal with at some point (some more than others). For example, I'm a Java developer, but I've had to write stored procedures, triggers, Crystal Reports, etc. <br />
<br />
There's sort of a third category starting up in our company comprised of Flex developers. It's small, but it's growing. BTW, if you haven't checked out Flex, take a look at it. RIAs seem to be the way web apps are moving. <br />
<br />
As to the workplace flexibility, I've found it really varies from shop to shop. The job I'm in right now is *very* strict on what they'll allow and what they won't as far as technologies go. You can introduce technologies that really add to the application and make your job as a coder much easier, but odds are it won't pass the code review. I remember one time I wanted to introduce JQuery in order to facilitate some drag-and-drop functionality, and that was very quickly shot down. A few years ago, though, I had a development job where they pretty much turned us loose and just said "do whatever you need to do to get the product built."

Back in my day the designer and teh coder were one and the same. There was a job titled programmer before the days of the computer and it was a union job. So, to allow the System Analysts/Programmers [designers/coders] to be non-union the company created the title "Systegrammer" for the combined position. The next company i went to called the combined job "System Analysts" and coders were "programmers." <br />
<br />
Anyway, congratulations on doing the design!

Thanks for commenting! :D<br />
I sure do have it nice, the other day I even got to design for the first time. I didnt event know I could design! I just started it as a sketch to pass on to the designer, but in the end the designer said I had done it really well and nothing else needed to be done to it!

I don't think they are all like yours by a long shot. Although the days of big COBOL or Assembly shops are long gone I bet there are still shops where you code in one language one big application all day, day after day. It sounds like you have it nice.