I have talked a little faster today but still a bit longer than I had wished for. I’m excited to bring good news about Blogrite, I’m steadly growing my knowledge on Ruby. Rack is really interesting, I’m loving how simple and easy to learn it is so far.
Testing is fun when you start to think of features you want to implement and quickly draw a quick test that will fail and you try to make it pass. I can’t wait to start the refactoring phase, when everything is working the not-so-right way.
Still not much to show you, sadly. I’m having trouble setting my tests up so the rest flows well. If you guys help me out on this, I will be sure to mention you in the following video, you deserve it.
It’s the first time I am writing any tests at all, I’m dead serious. Please bear with me, I’d appreciate your help in guiding towards the magic of TDD. Thanks guys.
What I noticed already
I chose Minitest after Rspec because it’s leaner, which is what I want for now.
Requiring ‘minitest/autorun’ will run my tests automatically.
The class to inherit from is Minitest::Unit::TestCase, not from the Test module.
I’m still missing stuff like how to require and autoload right. I’m pretty sure is wrong with that.
I’ve posted my first video about Blogrite. It mainly states initial thoughts and motivation on the project.
@dhh started a heated discussion on Rspec vs Test::Unit, right after I finished the recording. I must admit he’s a genius and he actually made me reconsider Test::Unit again, since it is considerably lighter than Rspec. I’ll have to think about it.
Truth: my blog and I have been apart for a while. Another truth: I’ve been reading more about Ruby. In fact, the more I read, the more I want to. Also, I’ve been growing tired of certain things:
PHP is not it anymore.
WordPress or Drupal are top notch. I don’t need top notch; I want to publish content easier and faster.
I want to learn Ruby the hard way. I want to learn how to test, I want to learn how to build a gem, how to use Rack, all of it. Only then I’ll be more confident enjoying the full power of Ruby.
I don’t want to depend on a database to publish my content. I never saw that much sense in storing articles inside a relational database column. I love Git and it seems it is capable of storing the content I want.
I’m sick of 10+ spam comments a day.
My next dare: a git + ruby based blog. So, I’ll be posting several articles on how I’m doing. If possible, I’ll post videos too. I’ll make sure to use Vimeo since it accepts OGG (it seems lighter).
