Programming is hard

I was greeted by this on my Verizon account page today. My first thought of course, "Don’t you have a test case for this?" And no space between the period and the "Y"? Automated tests and proofread!

When to Write Code Tests

Michael Hartl on when to write tests based on his experience

  • When a test is especially short or simple compared to the application code it tests, lean toward writing the test first.
  • When the desired behavior isn’t yet crystal clear, lean toward writing the application code first, then write a test to codify the result.
  • Because security is a top priority, err on the side of writing tests of the security model first.
  • Whenever a bug is found, write a test to reproduce it and protect against regressions, then write the application code to fix it. Lean against writing tests for code (such as detailed HTML structure) likely to change in the future.
  • Write tests before refactoring code, focusing on testing error-prone code that’s especially likely to break.

❂ A Milestone

MakePastie In the App Store

Today is the first day that I have an application available in the Apple app store. That means I actually “shipped” something. Pause for dramatic effect.

Learning to program in Swift has been fun, but challenging. All of the programming I have done in the past has been procedural in languages C or Pascal. But, it’s past time to update my skills and start thinking in objects.

After attempting and deciding the iTunes U Stanford Class, is too advanced for me, I joined Treehouse at end of September and have worked through their Swift and iOS tutorials. So far, so good. The slower pace and hand-holding is nice.

Am I on the road to be an Independent iOS Developer? No plans for that, but I am going to finish the Treehouse tutorials and see where to go from there.

The app is a native client for the website. It is a free app with an iAd banner. You can find it on here.

Update:  A good exercise, but the app was removed when pastie was shuttered.