Summertime Coding: .NET or Ruby on Rails?
May 09, 2008

Now that the semester's over, I've got a decision ahead of me. I've two paths to go with my free time coding, Ruby on Rails and continuing with learning awesome new stuff that's incredibly useful and cool - or .NET and strengthening my professional coding to excel more at my current place of employment. Oh, what's a boy to do? You may have noticed that my Caturday page is down. I'm split in between redoing it in .NET or making it into a cool RESTful application through Ruby on Rails (lawl, how does .NET know REST? It doesn't.). I've now got two viable dev environments, so that's no longer limiting me... it's just a choice between personal growth and professional growth... oi.

I sat down yesterday to do some work on it in .NET, and was reminded of how much work it is to get an object saved into the database compared to Ruby on Rails. However, when I go back to work I'm impressed with how neat it is when all the groundwork is finally laid and everything works. Humungous upfront fixed cost for some neatness in the end (.NET) Vs. tiny upfront fixed cost for some neatness now (RoR).

I'm still not sure what I'll end up doing... the great Summer question.

---

Your Name Required

Web Site

E-Mail For gravatar support

Write: dog Required

Das Comment

Post!

Thank you for your comment!