Erik Veenstra wrote:
> I've some comments, on almost all code in this thread. Feel
> free to ignore me...
>
> All code is "polluted" with meta-code stuff and "class <<
> object" stuff and "instance_eval" stuff and "class_eval" stuff
> and other stuff. That doesn't feel good. Well, you need this
> code to do the trick, but...
>
> It's usually a good idea to separate business logic and low
> level code. The novice programmers and mediocre programmers can
> concentrate on the business level code, while the more seasoned
> programmer can write the low-level code. The novice programmer
> is the user of the code made by the smart guy.
>
> The novice programmer only sees clean code: He understands what
> he is doing and is happy. Smart Guy is the, well, uh, smart guy
> and is happy too. Everybody's happy!
>
> I've mixed business code and low-level code myself, in the
> past. After one month, I simply couldn't read my own code,
> solely because I was mixing both levels. So, even if you are a
> smart guy and the only developer, it's still a good idea to
> think and code on different levels.

--- snip ---

Erik, thank you for pre-empting my next challenge and giving me a good
lesson in structure. Making the transition from mediocre to smart could
be more about structuring the code than knowing the language better ;)

James