Half-time Celebration and Revision
[CFL2M] CF Modernization Journey: Where Are You Now?
Congratulations! You’re halfway to completing full-on CF Modernization! This email is a recap of what we’ve covered.
If you read the last email (it was all about optimal configuration for your test server, dev server, and production server), it means you’re over 50% finished with this e-course. Congrats! If you missed it, please go check it out.
Now, here’s what we’ve covered in our CF Modernization journey so far:
This lesson taught you how to get rid of your spaghetti code. You pulled out code that looks similar and put it into several functions that have new parameters.
This lesson tackled the importance of performance monitor tools that help diagnose crashes and pinpoint where the problems lay. You were presented with two options for a performing monitor tool: FusionReactor (our favorite) and Adobe CF PMT.
This email focused on the significance of having consistent development, test, and production environments, and how automation minimizes bugs and ensures reliable application performance.
You downloaded Docker and began automating your environment setup to avoid manual errors and inconsistencies.
We introduced Docker as a powerful tool for containerizing your environments, ensuring that development, staging, and production settings are perfectly mirrored to eliminate discrepancies.
You applied version control to your Docker configurations and used CommandBox to spin up ColdFusion servers and had another CF dev test it out.
This lesson covered the dangers of hard-coded values. You sought out and listed all hard-coded values and replaced these magic numbers/values with descriptively named variables.
We explored the importance of source control, highlighting how Git and Bitbucket can prevent your code from being lost or overwritten, facilitate bug tracking, and enhance team collaboration.
You downloaded Git or Bitbucket and now have a source control system.
The importance of a separate testing environment was underscored, highlighting how it helps catch bugs early, ensures your app can perform under pressure, and protects your live environment.
You used Docker and CommandBox to set one up, and you ensured that it is configured identically to your production environment to prevent discrepancies.
If you’ve done everything already, then high-five and pat on the back to you! If not, let’s get you caught up.
Aragorn Action Step: Review the list above. If you missed any emails or have yet to complete the action step, go back and do it!
If you’re all caught up, then I say you deserve a chocolate mocha… or maybe a hobbit-sized martini! Whichever one feels more appropriate 🙂
To your achievement!
Michaela Light,
CEO TeraTech
PS These action steps can add up and may feel like a lot, especially if you’re dealing with a crashing server with thousands of bugs that are nearly impossible to track properly.
Hiring good CF developers is hard. You don’t need to go through that process.
If you prefer a “done-for-you” service, hit “reply”. My team and I would be happy to help.
If you’re enjoying the DIY approach, then stay tuned!
Next on your CF journey: Explore some great tools that will help you run security checks to keep your app robust. Be on the lookout for the next email.
