Reading The Programmer's Brain by Felienne Hermans - one of the rare books that underpins recommendations with studies and solid evidence - one question that kept creeping up for me is how different processes, practices and technologies that are in use nowadays (domain-driven design, different concurrency models, async code reviews, test-driven development, pairing, story mapping) impact cognition. Intriguing to think about!
Wizardzines, where Julia Evans shares amazing comics on topics like How Containers Work and HTTP, has expanded to include questions, where you can test your knowledge acquired reading the zines with some trivia, and experiments, a collection of useful playgrounds for e.g. nginx configuration.
I somehow missed these awesome updates (and that there are print versions of All the Zines!), made my day today.
LinkedIn, of all places, reminded me of this gem of a quote from Alan Cooper in a foreword of User Story Mapping today:
It’s entirely reasonable that programmers build software one feature at a time. That’s a perfectly good strategy, proven over the years. What has also been proven over the years is that, when used as a method for designing the behavior and scope of a digital product, one-feature-at-a-time yields a Frankenstein monster of a program.
proceeds to gesticulate wildly in software
Such a great song. Their album is coming out in September and 🤞 it's going to be great. Because it has to, because I ordered it.
Was drumming and thinking about these great explanations of Parallelism vs Concurrency, concurrency models, etc. Music is such a great way to build an intuitive understanding for all of this.
Then tried to find some research in cognitive psychology trying to understand how engineers model parallelism and concurrency in their heads. Only came up with results trying to apply parallel processing in cognitive psychology research. Oh well…
Stumbled over this album by accident while looking for something else.Sneakily got to be a favourite in just a few days.
Also, unrelated, feeling the urge to rewatch some Unfinished London.
If you invoke the same sequence of commands more than twice, write a script for it.
If you click around in a browser to simulate the same sequence of events more than twice, use browser automation.
Reproduce that bug you are fixing with an automated test first.
Seriously, your time is too valuable.
Some content is going to go here soon.
I hope it brings you joy.