thwarted

White collar work may have been phoning it in (literally and figuratively), but the drop is probably more likely due to "Labor Productivity (Output per Hour)" being measured using revenue from things like the social, entertainment, and travel industries taking a hit in customer spend (an empty restaurant has less output per hour than a busy restaurant, for example). It's not clear to me from that page/graph alone that an increase in stimulus spending is a cause, vs a correlation, for the drop.

> I'm old enough now that I don't have a lot of my time left to "hand stitch an amazing tapestry".

Why not? What is the goal of "having an amazing tapestry"? Do you need to do increasing more things in the limited time you have left and making a tapestry isn't one of those things? What will you have once you've "finished" an amazing tapestry, just something to hang on the wall and look at? How does one "use" a tapestry after it's "finished" such that the act of finishing it is the most important thing? If you've finished it, will you get more enjoyment from looking at it for longer because it was finished sooner and thus the length of time you can look at it before you die is maximized? Exactly what you are optimizing for here?

> We get way too hung up on data; especially when it reinforces our personal bias.

While I don't disagree that we generally get too hung up on data, "It's a problem when the data matches the hypothesis" is an odd blanket interpretation of the scientific method.

> Software creation tools have been worked on for decades to keep fallible human coders out of trouble as much as possible.

And the LLM-based coding agents provide the ultimate scapegoat for those who consider "the LLM wrote this code" to be an acceptable, deflecting response when issues occur.

>averaged about 1.3 suggestions per sentence.

It likely that no response at all or "This looks good, no suggestions" are not possible responses. They haven't figured out how to detect when a conversation should just end or that no response is necessary and include that in the training data.

> Go uses the system store with an additional revoke/deny list in crypto/x509 because it allows updating a deployed application on an out of date or slow moving platform or OS.

Reminder: Neither the CVE nor the linked go alert seem to say that you have to recompile and redeploy your application with the new go version in order to take advantage of this change. Just updating the tool chain and go stdlib isn't enough, because this stuff gets baked into the resultant binary. This is unlike, say, python, Ruby, or java where updating the runtime may be sufficient, depending on your development and deployment model.

"master" is less controversial?

One of those facts that mortgage owners refuse to internalize: the party responsible for the payments is not necessarily living on the property. There is absolutely no reason in this century to assume that the mailing address for real estate mortgage related correspondence is the address of the property. Related: the assumption that if there are two names on a mortgage with given names that are commonly understood to be gendered, the parties are legally married.

To say nothing of client side decorations, which diverge the user interface among apps and remove control from the user to globally customize some aspect of their application window management/theming.

I got bit by this recently. Brave on android has no "forward button in the app menu, it only has back. Chrome has both forward and back in the menu. Both browsers support swiping from the right side to go forward in the history stack (although this seems to be overloaded with switching tabs in a tab group), which I discovered by accident. What's odd about this though is that the device has a global back button that is also used for backward history navigation, but that's been duplicated in brave with an additional back action in the menu, but the forward history navigation is entirely hidden and has only one way to invoke it: via swiping.

> they only started hiding them because it looked 'cleaner' to some UI designer.

They started doing it on mobile in order to give more screen real estate to the content area. This was then translated to desktop apps at the same time desktop screen real estate became a non-issue for everyone (a 32" monitor at 1600x1200 used to be a luxury, now it's mundane). Now no one knows if there is anything "below the fold" without initiating a scroll action, which just encourages people to further only focus on the above the fold content.

Interestingly the response to that was sites adding horizontal "progress bars" across the top of the viewport to indicate how much you had read. And with application and website control of the styling and operation of these standard widgets, everyone is slightly different, which increases time to become familiar.

It's been a race to the bottom, in the name of (the subjective at best) "clean design".

> Turns out typing in long listings from B&W hobbyist zines and then finding all the typos was a fine way to learn.

My mom and I used to take turns reading the code from the magazines out loud while the other typed the code into our Commodore 64. She used to say things like "I was just having fun, typing in the games and playing them, but thwarted was actually learning something" (no, my mom doesn't call me "thwarted").

> Agents use source control, too. It's a pretty important part of the development process to understand how code has changed.

This is a great idea, now they just have to use/do it. Maybe they can use it effectively by cloning the repo and having all the history at hand, rather than continuously scraping web pages with git content formatted for human brwosing.

In that case, you're not running a "shell command" from python, you're passing arguments to exec. A shell command would be a string interpreted by the shell, and you'd use that for shell syntax things like having the shell do variable interpolation or redirections as part of executing the command.