3 ms·
Nice list. Along the lines of post yesterday, I'd encourage the developer to use an IDE and gems as little as possible in order to truly get what's going on un
by pfarrell 15y ago
Nice list. Along the lines of post yesterday, I'd encourage the developer to use an IDE and gems as little as possible in order to truly get what's going on under the covers. Also, the moving on is an excellent point. I've recently started an app-a-month goal for myself (I'm married with 2 kids) in order to keep myself shipping. I don't know how many times I've rewritten my mp3 site since 2002 :)
Here's one more comment.
11. Add Unit tests to anything you've developed that you want to keep developing.
- excid3 15y agoTwo excellent points that I forgot to cover.
- Sapient 15y agoI would agree with your IDE point, IF the person doesn't know how to use the IDE properly. I used RubyMine when learning Ruby/Rails, after having used IDEA for years (Java), and the two things which helped me learn Ruby and Rails faster than anything else were code completion (for finding methods which I may have not found otherwise) and the Source Navigator (for want of a better term). Being able to Ctrl-Click on a method and instantly see the source for it(Whether in a gem or in Rails itself) was a massive time-saver when it came to understanding what was going on under the covers. Edit: Agree 100% with adding tests.