Why is it so important to have ideal ColdFusion developers on your team?
In a survey I did last year 17% of participants said they had incompetent staff on their projects. Which means bad code, more bugs, and bad team dynamics. Ouch!
There is a ten to one variance between the worst programmer and the best programmer. And the worst programmers actually have negative ability because they introduce more bugs than they actually produce good code!
Paradox: 85% of a programmers success is due to human factors rather than pure technical skills.
What are the true costs of bad developers?
- Bad code, more bugs, even server crashes
- Bad hiring increases turnover cost
- More management headaches
- Other team members moral goes down
- Learning curve and training time
- Days lost to changing team members in and out
So you are probably asking yourself what is an ideal developer like?
Here is my take on this:
An ideal developer:
- Writes great programs that users love to use
- Code is easy to maintain
- Works well in teams
- Has few bugs
- Is good at solving problems in a simple way
But you only find this out once you have hired them. So! I look for character traits that predict this behavior ahead of time in the interview process.
What 7 character traits does an ideal developer have?
- Coding conventions
- Thinking and Planning
For example Humble
- My brain can’t take in the whole program at once – uses coding crutches
- Egoless programming – doesn't take their code personally if others need to change it
- Rewrites complex code to make it simpler to read
- Gets their code reviewed by another developer
- Asks for help if stuck for more than 15 minutes on a problem
- Holds back Murphy’s law with defensive coding methods
- Gives examples in comments
- Reference Change Tracker issue# and Description in comments
- Documents algorithm used in comments
These traits are from a user group talk I gave on “Guru Coders”. If you want to read about the other 6 traits in more detail I posted the slides on my LinkedIn profile. And if we are not connected on LI already I invite you to connect with me while you are there!
And to continue learning how to make your ColdFusion apps more modern and alive, I encourage you to download our free ColdFusion Alive Best Practices Checklist.
Because… perhaps you are responsible for a mission-critical or revenue-generating CF application that you don’t trust 100%, where implementing new features is a painful ad-hoc process with slow turnaround even for simple requests.
What if you have no contingency plan for a sudden developer departure or a server outage? Perhaps every time a new freelancer works on your site, something breaks. Or your application availability, security, and reliability are poor.
And if you are depending on ColdFusion for your job, then you can’t afford to let your CF development methods die on the vine.
You’re making a high-stakes bet that everything is going to be OK using the same old app creation ways in that one language — forever.
All it would take is for your fellow CF developer to quit or for your CIO to decide to leave the (falsely) perceived sinking ship of CFML and you could lose everything—your project, your hard-won CF skills, and possibly even your job.
Luckily, there are a number of simple, logical steps you can take now to protect yourself from these obvious risks.
No Brainer ColdFusion Best Practices to Ensure You Thrive No Matter What Happens Next
Modern ColdFusion development best practices that reduce stress, inefficiency, project lifecycle costs while simultaneously increasing project velocity and innovation.
√ Easily create a consistent server architecture across development, testing, and production
√ A modern test environment to prevent bugs from spreading
√ Automated continuous integration tools that work well with CF
√ A portable development environment baked into your codebase… for free!
Learn about these and many more strategies in our free ColdFusion Alive Best Practices Checklist.