There clearly are other factors involved in choosing technology in implementing a solution, than productivity, cost or return on investment. Monopoly on technology is nothing new, it is apparently the historical tendency , the what happens to a technology that is relatively open ( science ). On the other hand, status quo is of benefit to a lot of participants; an ecosystem does not develop around instability.
If you don’t care for all of that, since you are fronting the $$$ to get your vision, it’s things like this light read that should wake you up.
You are settling for less than you should from your software development investment if your work force, off shore , near shore, co-located or telecommuted , are NOT making use of Ruby on Rails.
You are being fleeced friend.
This year I’ve been able to leverage Heroku for the benefit of my employers. Two projects which were urgent, and had to be put in place in the middle of an IT infrastructure transition pushed by the merging of companies.
The experience has been overwhelmingly positive technically. Even while struggling with Ruby 1.9 encoding problems, the ridiculously productive community and tech folks @ heroku were able to provide a solid scalable and cheap platform.
Heroku and Taps simplified deployment pains , helped make smooth database nightmares of yesterday.
I highly recommend Heroku; it is as painless a hosting environment as you could ever wish for.
Make use of Rake in your miscellaneous migration tasks. Migrations are geared for database changes all or nothing is best since backtracking always is risky. Add your own application rake tasks to handle additional record creation, default settings, app specific stuff. Model classes are best for methods since you can test on console and tinker, but once you are there, a rake lib gives better control for the task at hand, lets you add on tasks without affecting the app core. All deployments I’ve used have handles to rake which can be used on demand.
Sofware professionals are always playing catch up to the books, to the best practices. to the certifications game.
This is the kind of analysis that blows my mind away. How many people will go back and revisit old assumptions?
When DeMarco published this paperHow many PMP professionals turned around and said , ok we are wrong?
This is a fast moving world; there are many thriving niches which will die out and should die out soon.
What else is new
mysql gem is in the process of being fixed. But for those experiencing deployment nightmares where suddenly switching the db makes all hell break loose.
mysql gem drop in fix for rails app
Set your language environment variable before kicking off your app, or set it in anyway you like.
Worked in Windows / Ruby 1.9.1 and Centos 5.4 / Ruby 1.9,1
Just a quick tip for those who have banged heads with sorting issues. In particular when working accross database technologies, you may end up getting bitten by default behavior differences.
So here’s something to keep in mind, Indexes are to Sorting as Hardware is to Software.. You can define default order behavior if you have the right index.
How did this come up recently for me? Sorting differences on a multilayer ed hierarchy of data , never noticed anything until deploying to production which used PGSQL instead of MYSQL