3 ms·
Even in dev, you have to basically code in irb in order to verify everything works.
by itake 4y ago
Even in dev, you have to basically code in irb in order to verify everything works.
- jeltz 4y agoNonsense. I used to be a professional Ruby developer and that is nowhere close to the truth. While I prefer static typing it is not hard at all to code in Ruby once you have learned the basics and I almost never used IRB other than when I was a beginner.
- pantulis 4y agoIt's good practice to use irb to quickly check stuff or inspect the programmatic surface of a new library. But that's a Ruby feature that you don't have in other languages! In no way its mandatory to code inside irb. Most of my time was spent in Textmate or Emacs.
- itake 4y agoHow many different ruby projects did you code in? Once you have memorized the global state on a project, you can rely on your intuition and rely less on irb. But anytime someone introduced a new gem (namely act_as_paranoid) or writes a new concern that modifies defaults, then you're back to need to do live code.