It’s really heartwarming to see this idea resonating.
Good advice on writing code that is understandable to your fellow humans (and your future self).
Breaking down programming tasks into smaller chunks …and naming things.
I’ll take a piece of paper and write the function names I’m going to implement. Or I’ll do it directly in my code editor, with real functions or comments.
It allows you to focus on one problem at a time. When you’re writing those function names, you are thinking about what the code should be doing. When you’re implementing the functions, you are thinking about how the code should do it.
As well as compèring the event, Chris took the time to make notes at the Clarity conference, dedicated to all things patterny.
When you’re struggling to write something that sounds clear and sounds human (two of the essential basics of a good blog post, I’d argue), just use the words normal people would use. The best way to find out what those words are is to try talking the thing through to someone who doesn’t know anything about it. Remember what you just said, then write that.
A useful text editor that analyses your writing for excess verbiage and sloppy construction. It helps you process your words, as it were.
Am I buzzword or not?