4 ms·
Yeah, hard to figure out what is going on here. I wish that procto code was more documented. Too much class level and module level munging morphs code into
by tarr11 11y ago
Yeah, hard to figure out what is going on here. I wish that procto code was more documented.
Too much class level and module level munging morphs code into a sub language only readable by the author.
I am generally supportive of this, though, if it masks enough underlying complexity.
In this case it's just syntactic sugar.
- catnaroek 11y ago> I am generally supportive of this, though, if it masks enough underlying complexity. In general, anything that makes the static structure of your program less discernible to whoever has to read it, can be considered technical debt. If you find yourself doing lots of dynamic metaprogramming, chances are you need to rethink your application's architecture.
- 33degrees 11y agoThe code itself is well documented and actually quite simple; worth a look https://github.com/snusnu/procto/blob/master/lib/procto.rb https://github.com/snusnu/procto/blob/master/lib/procto.rb