snapspans

I think the baity headline words "Taught in" should be changed to "Covered by".

Still working out how to read it (from just a glance at your link it looks like it ought to be investigated, or interpreted):

Caption:

"Fig. 2. The feeling space. (Upper) Two-dimensional map of the feeling space based on the sorting task average distance matrix between items arranged by t-SNE and clustered with DBSCAN. Color coding indicates cluster structure; gray feelings do not belong clearly to any cluster. Colored items with black edge are DBSCAN border elements. To retain the information of the distance matrix the closest three items for each node are connected with lines. Thick dark lines are showing distances that belong to the top 33rd percentile of the visualized lines (i.e., the closest items). (Lower) Heatmaps showing how strongly each basic dimension of subjective experience is associated with each discrete feeling at each location of the feeling space. Color coding shows the relative intensity as median z-score (as in Fig. 1) from high (red) to low (blue)."

Edit: The second image you linked would be perfect for the refrigerator. Great observation. (I'm not sure if I'm feeling "sadness" or "laughing".)

What a beautiful way to say "after thinking about it": "in the light of a cooler dawn".

Five things. Any more and I'd begin to lose track of subscriptions, or get less use from them while the money continues to flow.

I would argue there is another important benefit than the takeaway suggested in the second sentence of [1], that is the attention to architecture choices that allow for simple or complex (costly) refactoring later can engender more forward-looking awareness in the team's culture.

[1] "One approach I use when mentoring developers in this situation is to ask them to imagine the refactoring they would have to do later to introduce the capability when it's needed. Often that thought experiment is enough to convince them that it won't be significantly more expensive to add it later."