Ruby on Rails: another deployment, another 500 error. If you’ve had these problems in the past like I have then you probably already know about the pitfalls of your database.yml, your routes.rb, and making sure your bundle and rake commands run in RAILS_ENV=production. And don’t forget about rake assets:precompile! But if you get stuck like I did today, you precompile your assets and you still get an error in your production log that says an asset is not precompiled? Well I found the solution to that problem here. Thanks Chris Oliver!

‘Good enough software’ is rarely good enough. It is a sad manifestation of the spirit of modern times, in which an individual’s pride in his/her work has become rare. The idea that one might derive satisfaction from his or her successful work, because that work is ingenious, beautiful, or just pleasing, has become ridiculed. Nothing but economic success and monetary reward is acceptable. Hence our occupations have become mere jobs. But quality of work can be expected only through personal satisfaction, dedication and enjoyment. In our profession, precision and perfection are not a dispensable luxury, but a simple necessity.-Niklaus Wirth 1997