David Tattersall talks about “CF State of Union Survey 2017” in this episode of ColdFusion Alive Podcast, with host Michaela Light. David is the CEO of Integral, and is building FusionReactor, fusion analytics and fusion debug.
“I think what the ColdFusion guys want or are looking for with that is provide a platform that enables ColdFusion to be sort of a core component of an architecture that's also connected to other technologies. It's enabling other technologies to be more easily connected to CF, which is a great thing really.” – David Tattersall
Episode highlights
- CF State of Union Survey 2017
- What version of CFML does David prefer
- API Manager
- Management systems
Mentioned in this episode
Speaker details
David Tattersall is the CEO Intergral Information Solutions GmbH.
Links
Interview transcript
Michaela Light: TeraTech ColdFusion consulting. David, tell us a little bit about yourself, David. Who are you?
David T.: Hi. Who am I? My name's David. I'm the CEO of Integral. We're going to build FusionReactor, fusion analytics, and fusion. I'm working from home today, so this is my home office in the background.
Michaela Light: What a wonderful home office. We're here to talk about the state of the ColdFusion union survey this year. What were the most interesting things you saw in that, David?
David T.: I'd say highlighting some of the most interesting things, what struck me was actually it was the first question, what version of CFML engine do you use? Check all that apply. I think in the past looking at the previous state of the union surveys within, sort of let's say a year of releasing a new version of ColdFusion, typically the number of users using that version had pretty much reached the number of users who were using the previous year's, or the previous version.
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
ColdFusion Alive Best Practices Checklist
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.
