andrewgilmartin

One aspect not covered is how varied and wide ranging across the code and deployment platforms maintenance is done. One day you are tracking down a problem that's found to be caused by picking characters from UFT strings using indexes, and the next day the problem was an asynchronous job assuming all exception sub-classes of a common super-class can be ignored. These context switches physically hurt.

And yet low-speed vehicles are allowed....

Low-speed vehicles are coming to Rhode Island streets https://turnto10.com/news/local/low-speed-vehicles-are-comin...

See also

Technicals: Non-Standard Tactical Vehicles from the Great Toyota War to modern Special Forces

https://www.ospreypublishing.com/us/technicals-9781472822512...

Clotted cream is my greatest loss moving from Dartmouth, Devon to the US. A vanilla ice cream cone with clotted cream and a Cadbury flake is unparalleled. And a Mother’s Bread sandwich with clotted cream and strawberry jam being next in line.

One of DEC’s later line of VT 100 terminals introduced white text and smooth vertical scrolling. It was totally unusable due to the CRT ghosting. Well, unless you like reading text through gauze.

Writing tools do influence expression. I recall Jerry Pournelle saying how using an early mobile computer with its 40 character screen width had made his sentences shorter. Others I have worked with have mentioned how Microsoft Word’s built in thesaurus not only influenced their word choice, but that that choice dated the writing to a specific version of Word.

You can get lots of metadata from Crossref.org. See https://www.crossref.org/services/metadata-retrieval/

Yea, let’s use an weak and undisciplined markup language in a powerful and highly disciplined programming language ‘cause a few HTML tags is too much.

It also stopped at the first compilation error. You didn’t mind as it placed the cursor at the error in the editor and a recompile was a keypress away.

I liked this article. We are, I think, quibbling over the author's terms and conflating person experience with industry practice. Fundamentally you will see the broader landscape of issues inherent in a solution if you understand the concepts underlying the tool than if you only understand the tool's surfaces. I vividly remember a networking problem that a gathering of our brightest technicians could not solve and (almost by chance) a passing physicist interrupted the gathering and said we had a harmonics issue.

Please, no. Let's not intermix <> code fragments with <> html elements. Have you witnessed the nightmare of reading and updating JSTL, for example?

If I had a nickel for every time I have used this pattern

... | perl -ne 'print "$1 $2 ...\n" if /some-regex-with-capture-groups/' | ...

No one has yet mentioned that the Design Patterns uses UML to elucidate its patterns. I think those diagrams work due to their limited scope. I hope those I have drawn with similar limits have helped others understand my and even their own designs.

Writing is used for understanding and for communication. These are two different activities. Ie, the prototype is not the product. Highly recommend the book Thinking on Paper, https://www.amazon.com/Thinking-Paper-V-Howard/dp/0688077587

> I find it inspiring that it has such readable and space-efficient interface, compared to current trends in many web apps.

Agree.

Always missed Pascal’s typed scalar ranges.

Undo and Save. Every application allowed you to reverse or abandon a change.