Show #226: Tips for Your Younger Self

Railo , ColdFusion Builder , Taffy , Adobe , ColdFusion 11 Add comments

This week Dave and Scott discuss a quiet release update to CFBuilder. Then they talk about Adam Tuttle's new book on REST as well as the difficulties he had when attempting to switch from Adobe CF to Railo.

They then discuss a recent post where a developer was looking for advice on how to upgrade from ColdFusion 6 to ColdFusion 11.  Dave and Scott have definite opinions on the subject.

Finally, Scott asks that if you were to have the opportunity to give one piece of programming  advice to your younger self, what would it be.

Show Link:






A little bit about our sponsor. Host Media is, among other things, a ColdFusion hosting provider. Click the link below for an exclusive discount for CFHour listeners using the discount code 'cfhour'

Host Media


Show Topic Links:

Secret CFBuilder 3 update?


Someone tried to update to Railo

Make stuff way faster: urandom


Buy Stuff


CFHour intro and outro audio created and provided by vocal talent James Allen:

8 responses to “Show #226: Tips for Your Younger Self”

  1. Phillip Senn Says:
    From a ColdFusion perspective, I would say to use stored procedures instead of cfquery.
    When I started using stored procedures exclusively, and the stored procedures could return _multiple resultsets_, it changed quite a bit of my coding.
    So a stored procedure named Order.WhereCustID would return in resultset1 the orders for this customer, but then in resultset2 the info about the customer and in resultset3 the info about any lookup tables like CustomerType.
    It moved the majority of the code out of ColdFusion and into SQL Server.
    I think the decision to go with twitter bootstrap was a good one. Specifying CSS for colors is very easy but using CSS for layouts is tough.
    I have Scott to thank for the bootstrap recommendation.
    I think learning JavaScript has been a good decision, as much as I have learned it. To me, JavaScript is hard while ColdFusion and SQL Server are easy.
    Railo has been a good decision for my personal projects.
    I don't think we're going to attempt moving over to Railo here at work though. At work, there would be financial consequences to something not working right. The pressure is off when it comes to my personal projects, so I'm freer to experiment with things like moving an entire project to Railo or rewrite everything using stored procedures.
  2. Phillip Senn Says:
    Oh, and I would advise to go ahead and move to cfscript as well, at the top of the page, before the html tag.

    Although I use components <em>a whole lot less</em> now that all the code is in stored procedures.

    I simply call the stored procedure from the page instead of calling a function which would then call the stored procedure.
  3. Phillip Senn Says:
    I think that we don't give credence to the amount of time that it takes to write computer programs. I'll give you an example. I woke up one Friday morning, having the day off and I had an idea for a simple program to write. So I sat down and started typing.
    All day Friday and except for a meal break, continued typing.
    I went to bed, got up Saturday and continued typing. All day Saturday. And this wasn't that hard of a program either. But by the time I added css and a little bit of JavaScript, it took 2 solid days of solid programming.
    What could I have done in those two days instead of sitting at my keyboard?
    Now, you might says "Well, you suck". But I don't think so. I consider myself a pretty solid programmer, comparing myself to others in the corporate world.
    So I think that even WE don't appreciate how long it takes to write programs, AND WE ARE THE ONES WHO WRITE THEM.
  4. Adam Cameron Says:
    My tip would be: read Clean Code: Indeed for a new dev, old dev, any dev, it's a vital read. It would have changed the way I developed code right from the outset, and I'd've been a better developer for it.

    As far as embarrassing cock-ups go... yeah, I've done an SQL UPDATE with no WHERE clause too. But I *did* have a back-up.

    Cheers lads: best episode for a long time. It was almost entirely on topic. Good work.

  5. Dan Kraus Says:
    Adam Tuttle's REST book is solid info. It's a quick read though. I think I read through it in an hour I think. I'd recommend it, not CFML specific.

    I'd tell my younger self get on the script wagon sooner. I feel like it encourages me to write cleaner, more concise code broken out into more functions, objects, etc.

    I'd embrace testing much, much sooner. I got into it with Rails but for some reason it just couldn't click with CF for some reason with me. Certainly had something to do with the tooling available in Ruby like RSpec, FactoryGirl, and others. Finding TestBox and and starting to explore MockBox and others to do it. Again, being test conscious will help you write better code that is pointed and specific.
  6. Sean Corfield Says:
    I don't know what tips I would give my younger self - the world was so very different then. I used version control very early on (sccs, then rcs!). I wrote a lot of tests (probably because I worked on compilers, interpreters, runtime systems and virtual machines - all of which traditionally use large test suites). Most of the books people recommend nowadays hadn't been written back then (e.g., the "Gang of Four" Design Patterns book appeared after I'd been doing OOP for several years).

    Probably the only advice I would want to have given myself would be: "Stick to Functional Programming as much as you can, despite all the other nonsense that comes along - FP will eventually go mainstream and you could be one of the leading lights of that community!" :)
  7. Sean Corfield Says:
    For those who want the history, sccs appeared in 1972, rcs appeared in 1982:

    rcs essentially evolved into cvs in the early 90's. svn appeared in 2000. git in 2005.
  8. No> Says:
    Probably the only advice ignored!

Leave a Reply

Leave this field empty:

Powered by Mango Blog. Design and Icons by N.Design Studio