I can’t think of a person that isn’t aware of modular counting. We do it just about every day… well, hopefully not while we are on vacation. But every time you look at your watch, and figure out how many hours you have left before your work day is over, and it is before noon, you do it. Read on →

First of all, you must have installed rubydoctest which can be installed as a gem, or from source. Source can be found here: rubydoctest and the handy gem install rubydoctest can be used as well.

I just want to introduce you to the tool. I find it handy when I want to verify things in irb, which I have open anyway, and it helps to document my code inline, or to have a .doctest file sitting next to my file (or in the ../tests directory) Read on →

Performance should be pretty close to the end of the list of things to do when programming in Ruby. Yes, it can be important to get the timing down on your code. But this is after you verify that it is running as you need it to, and it is actually usable. Read on →

Welcome to little random thoughts of Ruby… My topic tonight is about the prompt snippet I gave yesterday. I didn’t realize it, as often happens, but it was so simple, I had to add the feature.

I realized while writing another wrapper for benchmark and profiler, that it is pretty common to add chomp() to our gets. But there may be times when we want what gets, um… well, gets. Read on →

Hints for use:

1

name = 'Please enter your name'.prompt

I know that each time I want to ask a user for something, I need to write a way to ensure that the user sees the prompt, so that an appropriate answer can be provided. Read on →

I found the following snippet ( edited by me, for changes I wanted…) Credits are in the code block.