How Documentation Leads Me to Smarter Programming

“Okay, so these are the steps to take in order to run this process.

Step one: rename the file. Wait. Why would I rename the file? SSIS can do that for me in a script task. No need to bother the operator with that.

All right. Step one: copy the file to a staging folder…hang on….a script task can do that too. Let me just throw a File.Copy in there.

Step one: Open the Excel file and delete the header rows (1-5) on the sheet labeled “Data”. ¬†Okay, step two. No, no, I can just tell the connection manager to ignore the first five rows. Let me go fix that up. There, much better.

Step one:…”

3 Responses to “How Documentation Leads Me to Smarter Programming”

  1. February 27, 2013 at 9:30 AM #

    So step 1 is: Profit$$$ I’m a bit confused :)

    • Doug Lane
      February 27, 2013 at 10:05 AM #

      I buried the secret to profit somewhere in the post. Keep reading until you find it. :-)

  2. March 7, 2013 at 6:12 AM #

    That’s funny. I keep having that experience as I learn more PowerShell – “No no… why am I declaring all this stuff, I can make it one line!”

Leave a Comment

You must be logged in to post a comment.