Building websites/apps for almost 20 years. Full-stack, Ruby + Rails since 2006. Hobbiest woodworker, maker, husband and father of two. Callsign W6AKJ.
Thanks! I was working on a random controller or presenter in Rails a couple of months ago and after some refactoring I sat back and looked at it and realized it almost looked like some pseudocode that I'd write on a whiteboard when planning. I looked through the codebase and ended up seeing that pattern everywhere and realized that's basically what most "good" code ends up looking like—I just hadn't heard anyone phrase it as such!
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.
Thanks! I was working on a random controller or presenter in Rails a couple of months ago and after some refactoring I sat back and looked at it and realized it almost looked like some pseudocode that I'd write on a whiteboard when planning. I looked through the codebase and ended up seeing that pattern everywhere and realized that's basically what most "good" code ends up looking like—I just hadn't heard anyone phrase it as such!