software job advice

[HAULN-SS]

So, another quick update and/or vent. I actually love the type of work I am doing now. Code Optimization is fun. Working in an R&D environment is fun. I basically get to read and/or shit on thesis papers and stuff all the time. A lot of the code we work on started out as a research topic in university at one point recently, so it's kinda nice to be working on cutting edge algorithms and such. I also have completely refreshed on my math skills that at one point were starting to slip. This job has completely re-upped me in the areas of vector calculus and other topics I wont bore you with.

On the downside, I guess the downsizing of aerospace projects due to the economy is starting to trickle down. I did get a raise to take this job, but there has been a trend (openly discussed among management) to give people lesser performance reviews, and the raises in general are smaller this year than in years past. This kind of pisses me off (moreso about them actually saying they are going to give people lower reviews than the raise part).

So, I think I am going to look around about finding a new job once I finish with my masters this year. I am in the 3rd to last class right now. The bad news is, since I do kind of like this work, my options for next job are going to be more limited to government agencies and other companies trying to solve large problems as fast as possible. Probably in a lab closer to this area than New Mexico too..I kind of decided even though I like BFE, that is just a little too far out.

And just as a general PSA to up and coming, or existing software people...I think if you are looking for something different to do other than enterprise application programming in .net or java or whatever..looking for a job in code optimization isn't a bad way to go, especially if you have a math background. Most of my job involves first trying to figure out what partial differential equation some code is trying to solve, and see if they are even using the best numerical method possible. This work comes before even writing the first line of code. We also pretty much work in quick spiral development cycles too, which I like.