6 replies to this topic

[njr1489]

It's kind of ironic when the only job you aren't interested in may actually want you. As a PHP developer, they wanted to see what I could do, so they give me some of their code to work with. Little did I realize before I went there, their code is horrible! I spent an hour looking at what their code does and how their database is structured, it's just very cumbersome to work with. To top it off, the environment is business casual which was very odd to me. A lot of jobs I know of that are programming have no dress code. It really sucks knowing that, when your last job in doing the same thing let you go in your gym clothes.

I'm not sure what I should do, my friends tell me I should just get employed there, because if I think I could write better code and fix theirs, I might get promoted, or eventually replace someone higher up. Although that is possible somewhat, I just don't think my skill level would progress nor would I be happy there. I did however, ask for somewhat of a hefty amount at my level.

What's the best possible course of action for me? At this point if I take it, I'm just going to continue doing my own work on the side so I don't feel that my skill would degrade at all.

[mrlemke]

That depends on you. I'd take the job in a heart beat, even if it is PHP and web development. It beats working at a TV station. After all, it's a job, and the primary goal is making money and not having fun.

[njr1489]

Well I didn't mean it that way. When I was writing PHP in my other job I found it fun. It's just their code I've seen that has me look the other way.

[Alexander]

If you want the job to fix a lot of code and write code, then that is an alright job but you may not wish to take it if your goal is to to stress your skills and learn too much new, it appears to be a very limiting job. I can say about promotions, some people do not like changes and will stand by the old bad code, especially if somebody new wants to rewrite it. I only mention this because I had seen some annoying higher-ups before prevent people from making major changes, although it could go either way.

[WingedPanther]

What you'll be doing is Refactoring. I'm reading a good book on it right now: Amazon.com: Refactoring: Improving the Design of Existing Code (0785342485677): Martin Fowler, Kent Beck, John Brant, William Opdyke, Don Roberts: Books

It's actually a valuable skill that you'd be working on. I've worked in both business casual and casual environments. You get used to the clothes. Just buy comfortable ones.

I've worked on poor code before, and it's not fun, but it can be VERY satisfying to see the result when you clean it up and fix a few bugs on the way.

[njr1489]

Hmm, I haven't thought of it that way. That is actually a useful skill as I would eventually run into a similar problem anyway. Thanks, I'll take a look at the book as well. I could use a change in how I see existing code.

[Muted]

njr1489 said:

What's the best possible course of action for me? At this point if I take it, I'm just going to continue doing my own work on the side so I don't feel that my skill would degrade at all.

Keep the job? Duh? I'd kill for a programming job right now (or any)...!

If nothing else (as WingedPanther pointed out): It'll give you invaluable experience, and: EXPERIENCE!
What will you put on your next job? XX years working as a PHP developer, refactoring code. :c-^_^:
You may very well inadvertently be promoted, which would be all the more pleasant!

Good luck with it! :c-grin: