[bjelkeman-again]

I didn't downvote, but maybe it was the tone. "These ppl are pure scum" qualifies for me for others than some devs with other motivations than what I have.

There are definitely good jobs which one can be passionate about out there. I didn't easily find that job myself when I was sick of my job and ended up creating it instead. This industry offers so much potential that I feel it is nearly only a matter of looking around to see what needs to be done. Not a given one will be successful, but doing ok so far. Done give up, look around yourself, the good stuff is out there.

[fat0wl]

thanks... I think the reason I get a bit heated is because I come from an arts background actually. There are a lot of slippery slopes in industry, and now I am on one. It disgusts me when I see that my peers are just tumbling over one another to reach the bottom first, just to put another $5/hr on their rate whereas I used to work with people who didn't care if they spent their whole careers as penniless musicians so long as they got to experience the feeling of genuine pursuit of passion. I see a lot of devs implementing a mess of seriously nasty sweat-shop code with tools/langs they only embraced because of some perceived gap in the market. It seems unethical to me as a developer to do things in an inefficient manner, or its at least sad in that it means you have no sense of personal efficacy or investment in your own growth (beyond how a corporation views you).

A lot of tech feels like a very spiritually empty game, and I resent it for becoming this gruesome when really programming can be a beautiful pursuit as well. I'm trying to be patient, there is a company that has expressed interest in me that is much more into embracing proper design paradigms and modern approaches at least. At my current gig we are handcuffed by lots of legacy code, layers of bureaucracy, "Senior Devs & Architects" who are really at about junior level, and people who are difficult just for the sake of slowing down the pace of work.

Even in academia, I saw a lot of music tech students receive their masters degrees only to promptly jump into a tech bootcamp so they could then assume the position of low-end web dev rather than use any of the audio research skills they spent years trying to assimilate (bit of pot calling the kettle black here but I purposely ditched Ruby for a Java-based job so that I can get back into coding DSP & performance-intensive research apps -- I also spend a lot of time decompiling audio libs).

Living with this job for 2 years has been maddening & I am relieved that I have enough on my post-academia resume now to escape it one of these days. I really need to meet artists who code. Have even been considering going into indie game programming just to meet more of those types, though really my passion is more in electronic art than gaming (but electronic art is barely an industry at all outside advertising!)...

[digisth]

You (and others with real software development skills and drive) are in an incredible position today. You've graduated into a very exciting market (I went through the previous boom and it was frenzied, but this is one is even more so) with opportunities everywhere. If you can't seem to find anything on the 'art and design technology' side, take a look into organizations like EyeBeam [http://eyebeam.org/] and AdaFruit's job page [https://www.adafruit.com/jobs/] to start with; they may not be trivial to find, but some are out there. Before I became a software developer, I was in audio engineering (didn't last long) and am an occasional musician, so I've seen both sides. There is definitely an incredible amount of boring stuff out there, but there's also exciting stuff to be found.

Many people do just jump in for the money, and others in this thread have addressed it, so I won't except to say that there are people who start out in an industry because they need the money (for example, I had to live on my own and start work at 17, no familial support), but then realize they really enjoy it and stay for the other stuff: problem solving, puzzles, building elegant things, and all the rest. Perhaps not most, but there are some.

As far as the passion vs. profit stuff, there's no denying that there's a serious tension there, and that's not going anywhere anytime soon. I've dealt with this too, and I saw three choices:

1) You can live like a pauper in an expensive area/decently in a very cheap area and do what you enjoy, even if no one ever buys it. There are people who do this with code - I've seen plenty of indie game devs pick a cheap area in the US, work the occasional freelance job, and spend every other moment working on their games. This can be a totally valid path if you're OK with its limitations. You know what this is like from the art side already, too.

2) You can try to get wealthy and then do whatever you want - no more working terrible jobs, being paid a fraction of what you're worth, being engulfed in [other] company politics, working for others when you'd rather be working for yourself, etc. I'm sure many people of us here on HN are doing exactly that.

3) You can try to find a decent compromise - some companies will give you 5% time, others may pay you to just do research (a previous company I worked for paid a few people to do nothing but work on an audio/3D visual coding framework, for example), others simply hit that sweet spot of giving you interesting stuff to work on for decent money.

[fat0wl]

thanks for the suggestions. I actually spent some time as an "intern" (hang out making art & doing whatever) at Harvestworks [http://www.harvestworks.org/], which is very similar to EyeBeam. I just decided it wasn't for me when I saw that artists spent so much time on grant-writing just for a chance at a sum of money most of them (they were pretty tech-savvy) could make through a few days of freelance if they sharpened their coding skills a bit.

I didn't mean to come off as a spoiled brat chastising hard-working people. I definitely understand that folks have to take jobs and make a wage, not always doing what they want. My criticism is much more directed toward those who have reached the intermediate level but then choose to excel at mediocrity. I work with some devs who are shining examples of this. They use a rapid dev tool that encourages awful programming practices, and they jump from shop to shop leaving piles of code-dung behind. They are slightly jealous as I refine my Java skills to becoming increasingly more powerful & effective, but not to the point where they would actually commit to learning. Instead, they are content knowing they have a niche skill and will be consistently overpaid for poor quality implementations.

Anyway I digress.... your breakdown seems pretty deadon. I wish I had the stomach for #1 but didn't, so I thought it would be easier to do #3 to pave the way for #2 (I had this idea that working corporate gigs was the only true test of and exercise for my coding skills)....

I guess I need to find a better #3 or jump ship to 1 or maybe even 2 if I can handle a startup run... it's just hard to leave because the current gig actually doesn't work us very hard its just too much politicking within a very dull talent pool, kinda lulls me to sleep (though trust me I would take a more challenging job in an instant, its not about being lazy just lack of opportunities thus far).

[fat0wl]

thx... I think the reason I get a bit heated is because I come from an arts background actually. There are a lot of slippery slopes in industry, and I am on one. It disgusts me when I see that my peers are just tumbling over one another to reach the bottom first, just to put another $5/hr on their rate whereas I used to work with people who didn't care if they spent their whole careers as penniless musicians so long as they got to experience the feeling of genuine pursuit of passion.

A lot of tech feels like a very spiritually empty game, and I resent it for becoming this gruesome when really programming is a beautiful pursuit. I'm trying to be patient, there is a company that has expressed interest in me that is much more into embracing proper design paradigms and new approaches to back-end code. At my current gig we are handcuffed by lots of legacy code, layers of bureaucracy, "Senior Devs & Architects" who are really at about junior level, and people who are difficult just for the sake of slowing down the average pace of work.

Living with this for 2 years has been maddening & I am relieved that I have enough on my post-academia resume now to escape it one of these days.