I have been inspired by my previous blog post The joys of IT recruitment (and years of frustration)
To start working on a business idea for IT recruitment. The main premise of which is that an IT professional will be much better at vetting candidates for an IT job than your bog standard recruitment consultant.
I have started working on the website in asp.net 2.0 (C#) but then thought i'd try out ruby on rails for a couple of reasons
- See what all the fuss is about and learn something new.
- much cheaper vps hosting compared to asp.net
- excuse to improve my poor linux admin skills
I'll probably be blogging more on my trials and tribulations as i attempt to build the site using an unfamiliar language and framework on an unfamiliar OS.
But to start here are my first thoughts:
- Why do a lot of people in the rails community seem to have attitude problems?
- MVC is nice, but feels odd sometimes, (probably me being thick) ie: validation in your model? shouldn't business logic be in the controller? Is validation not business logic?
- mmm, no data access plumbing i can just get on with writing the app.
- GUI tools for mysql still aren't a match for sql server (wonder if Sun will improve these?)
- Don't like the convention that database table names are pluralised (orders instead of order) This is the opposite of what i was taught.
- Wish that migrations could work both ways ie: create a rails migration from an existing database schema.
- don't you just hate it when an open source project is not maintained (act_as_taggable)
- It seems current wisdom dictates that you should run rails on mongrel with apache acting as a proxy, what a pain in the arse, oh for right click, create website in IIS.