No, this is not a real Sinatra error :).
This is the personal homepage of Elad Meidar, a web developer and an entrepreneur specializing in Ruby on Rails. I hang around in Israel, and i am currently having the best time of my life over at Fiverr.com
I am a proud member of RailsBridge, Helping new Rails developers get into our world and also contributed a few Patches to the Ruby on Rails core.
When developing a new application, mostly when it’s being done personally and alone, can sometimes be a very complicated process. you’ll need to handle a whole bunch of other stuff than just coding (marketing, server setups even investors hunt) and it can sometimes lead you to a software neglection.
Don’t let it happen, run/compile your application every few days, keep it living in your head.
Sometimes you’ll start work on some big shiny feature (e.g. adding a kewl Google maps integration), but stop because you hit a technical bump (“What? no maps for Israel?”), or donít have the time to finish it (“Need to finish this Company profile by tomorrow”) and The source code is left in unfinished state.
You canít do anything with any of your code until this is fixed, and the longer you leave it, the more youíll forget and the harder it will be to get started again.
This is called a “broken build”, and is a big landmine because it impacts other peoples ability to work (And your ability to continue as well).
TIP #1: You started something? finish it before moving on to something else.
TIP #2: Stay in touch with your software.
Know these times when you wished you had a time machine? well, it can happen in the process of developing and application too.
People make mistakes, Always. When people make mistakes in the kitchen, the food comes out really bad and you call the local pizza delivery services and solve the problem. When a programmer makes a mistake or is doing a system wide change… you’ll need a ready to use Plan B around.
Source Control is the software world equivalent of a time machine, you can go back to a certain version of your application and rollback any changes made to your code and application, and by that, maybe reversing a very serious threat to your code.
If you havenít taken the plunge with revision control yet, I highly recommend looking at some of the free SVN or GIT hosting services post.
TIP #3: Save yourself, use a source control service.
As Netscape famously discovered a few years ago, throwing away existing code to start afresh is almost never a good idea. Resist the urge and make a series of small, manageable code re-factoring instead.
TIP #5: Never sink your own boat, pickup a bucket and start pulling out water
“mmm, Rails? or maybe Adobe Air? or maybe… maybe we’ll do the cool gears thing?”
Before doing anything ask yourself a simple question – “What are you actually trying to achieve?”, Spend some time with a pen and some paper coming up with a really clear vision of what youíre trying to create ó e.g. screen mock-ups, basic core functionality (yes, again) and if there is a process you are trying to imitate, go through it too.
TIP #6: If you donít know what youíre doing from the beginning, youíll have no chance of finishing it.
Tell people about your product when you have something to show, open a product twitter account when you have something to say, don’t rush yourself forward and try to stick the product or create a hype when you can’t back it up by at least screenshots or an actual product on the best scenario.
TIP #8: Invite people in when you have something to offer them to eat.
You're seeing this error because I think it is funny.