Mistakes

I respect mistakes as a useful tool for learning and improving a skill. We never get it right the first time. So here's where I'll document my failure and hopefully learn along the way.

Nov 21

One day of inaction

I started out trying to create the site with Expression Engine.  Then I hit some bumps in the road.  I couldn’t figure out how to create pages, so I dug around in the documentation and actually found a very useful screencast.  Things were going good and then I read the license, and realized that I would need written consent from the developers of EE to make the site that I want to create.  Blarg.

Then J contacted me assured me that I could move forward with tweaking our server. Then I started thinking about doing this project in Ruby on Rails instead of PHP. There are so many variables, and I feel like I’m stuck in “paralysis of analysis”.

Lessons learned:

  • You can’t assume that someone’s going to help you out.
  • Read the license.
  • Read the documentation before you poke around.  It’ll save you time.
  • Getting anxious over an imaginary deadline sucks.
  • Go towards the prize, not away from pain.

Comments (View)
Page 1 of 1
blog comments powered by Disqus