use Perl

• Good analogy (Score:2)

  by merlyn (47)

  I learned programming before debuggers became available. My theory was "understand what you write, never outwrite ahead of your brain". And when that failed, "add print until it works".

  I never realized how much this influences my coding style until I was recently in front of 30 people at a client location, writing some complex code in real time for them. I'd write three or four lines of code, run the program, then either rewrite those three or four lines if they didn't do what I expect, or I'd write th

  --
  

  • Randal L. Schwartz
  • Stonehenge
  • Re:Good analogy (Score:1)

    by jplindstrom (594) on 2003.12.16 13:18 (#26590) Journal

    I guess this small-steps way of doing things kind of requires a language like Perl where you essentially have no compilation step to prevent you from seeing what you just did.
    
    In a way it resembles the way of writing HTML: write, save, switch to the browser and reload in a quick sequence.
    
    So using a language which takes longer to compile, like C++ in a lot of cases, breaks the cycle, forcing you to write more and more code to justify a compilation (thereby verifying that you didn't outwit yourself).
    

    Reply to This

    Parent

    • Re:Good analogy (Score:2)

      by dws (341)

      Yeah, quick turnaround on the compile/link/run cycle is essential. I've been able to do Test Driven Development in Perl, Java, and now Python, but have thus far avoided the opportunity of trying it in C++.

      It's amazing how comforting it is to know that if you find a problem, changes are really good that you caused it within the last few minutes, and that you only have to take one step back.
      • Re:Good analogy (Score:1)

        by jplindstrom (594)

        Anyone with success stories of TDD in C++?
        
        I'm think I'm about to get involved in that in the near future, and I'd appreciate any practical tips and tricks.