Recovering interrupter with occasional relapses, lover of spreadsheets, blogger, programmer, adept debugger, conjurer of analogies, and probably other things.
When I create a class in Ruby, if I'm at my best, I always try to start with the following comment before I write any code:
The purpose of this class is...
I have a high degree of confidence that that intention will persist regardless of the implementation details.
This then follows with methods, but by the time I've written out the class purpose, the methods are (in the moment) somewhat self-evident. (I still go back and document the methods)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
When I create a class in Ruby, if I'm at my best, I always try to start with the following comment before I write any code:
I have a high degree of confidence that that intention will persist regardless of the implementation details.
This then follows with methods, but by the time I've written out the class purpose, the methods are (in the moment) somewhat self-evident. (I still go back and document the methods)