I couldn't be happier with my choice. It's a great job with good coworkers. (I guess I have luck in this department, never had a douchebag for a coworker in my life)
At my place of work we primarily use PHP, we use Moodle for our main workhorse but any company websites, contact forms, or whatever we may need is written in simple .php files.
Currently my coworker copy-pastes the header and footer HTML markup to many different PHP files. No, he does not even "include" that sucker in, he manually copy-pastes it. I can't argue with his results, he gets things done and ultimately that's what is important - however I'd like to show him (and the rest of our team) how a PHP framework like CakePHP can help us out in the long run.
MVC frameworks and websites go like bread and butter. He would declare his header and never ever ever have to copy and paste it somewhere else. Making changes to the header would be a matter of modifying the main layout, not each file. Benefits all around, not to mention a fantastic ORM library.
So here's my question: How do you introduce new frameworks, tools or paradigms to coworkers?
Here are a few of my own thoughts to get things started:
- Show a clear example of how this can benefit the team.
- Show how marketable the skill is to have. (This is tough but can be done if you can back it up)
- Show how it can lighten work for the team. (Less work = more fun for all = less chances for things to break)
This post has been edited by Sergio Tapia: 12 September 2012 - 07:01 AM