|
I've recently been assigned to work on a project written in PHP. I can't change that, and have no intention of really trying. However, this can't be an uncommon scenario. How do you motivate yourself to work on the project when the code you're looking at and producing constantly makes you want to cry? EDIT: It should be noted that this is pretty much the only on-campus job doing anything software related available at the moment, so "just change jobs" isn't really an option :( |
|||||||||||||||||
|
|
My tip would be to endure it, only if you see the benefit of learning anything from the language and all the processes or patterns that the project uses. You might gain something from it. The alternative, if you're risk-averse enough, is to look for another job. Which is certainly a good idea if your lack of the motivation is dragged down not only because of the technology used, but by the lack of understanding for good practices from your coworkers. There should be better things to do than to have your abilities as a developer stagnate. If you're not learning anything or gain anything from your job: get a better job. |
|||
|
|
If it's a contract or short term project, or something you'll occasionally need to support, just bite the bullet and do it, of course. If not, then look for another job or try to explain why that language could be a hindrance on the long term (if you can). In the first case, it's about being professional and not whining about personal preferences. In the second case, it's about being happy with your job and life. If what you need is motivation, I'd say start trying to find bits and pieces you enjoy in the language, and start a personal pet project with it so you have a stronger incentive to learn it more in depth. Try to do things that you like with it. If you like TDD, focus on improving the test coverage, etc... But in the end, you'll have to bite the bullet. |
|||
|
|
|
You design the programming language that you would like to use, then write a compiler that outputs the language you don't like to use. At least, that's what these guys did:
|
|||||||||||
|
|
Pick up your resume, and start looking for a different job. PHP is a powerful language, however its syntax is shitty and non consistent. At the same time start home project in the language you do want to work in, and if you can join an open source project. good luck. |
|||
|
|
|
How long is the project? If is it short just grin and bear it and think if it as good resume filler. If long term I would look for another job. |
|||
|
|
|
Really? You do what you do when you HAVE to work on ANYTHING you hate. You grit your teeth, dig in and get the job done. ..or you learn to be a little more easy going! |
|||||
|
|
If your employer makes you work regularily using tools that you "hate" (which is a very strong term), then perhaps you are in the wrong job? Being pragmatic is essential to profesionalism. |
|||
|
|
|
If I'm building something that someone wants with a language that I feel is capable of delivering the project without too many problems, I can get over it. What worries me is when they want functionality that may not be possible/practical or it takes longer than normal. |
|||
|
|
|
Its a learning opportunity. A couple of things spring to mind:
As a professional you have, substantially, to shut up and get on with it - the sooner its done the sooner you get back to using toys you like. That's not to say that you shouldn't express your unhappiness to your management at the start and at the end. But probably not in the middle. |
|||
|
|
