[ thoughts in tidy boxes ]

The 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 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

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…

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.