This is why Google is pushing SEOs to get their clients to codify and publish their domain expertise: while it gives them a way to filter signal from noise/slop right now (supposedly helping to "improve search experiences"), it also simultaneously extracts that experience into a consumable form for later training.
They really do want to know the ins-and-outs of the HVAC service business, for example, because they hope their agents will be handling it in a few years.
In many cases the really key idea that transforms the overall system design comes from working closely on the specific implementation details. Maybe you don't redesign the system this time, but you saw how you might do it, and you get ideas about how to do it the next time. The craft involves a back-and-forth between different levels of abstraction, and cutting that link does feel like we're sacrificing something.
> Earlier automation targeted physical and manual labor, where a worker’s identity was at least partly separable from the output. A welder is not the weld.
It comes through even worse in this later sentence, which at the very least tells you the writer has never met a welder.
There was also a period around the mid-2010s where I had the strong impression that lots of younger ambitious devs were fanatically promoting rust against C's undefined behavior mostly because it gave them a way to differentiate themselves from older seniors within organizations. (And I say this not as an old C diehard, but as someone who watched more than one colleague position himself as the 'rust guy'.)
It could be a symptom of how fragmented workflows are, which itself seems to be due to providers adding friction to guard against being integrated away by some larger platform.
You mention the technical aspect (readability) and others have suggested the aesthetic, but you could also look at it as a form of rhetoric. I'm not sure it's really effective because it sort of grates on the ear for anyone over 35, but maybe there's a point in distinguishing itself from AI sloptext.
Incidentally, millenials also used the "no caps" style but mainly for "marginalia" (at most paragraph-length notes, observations), while for older generations it was almost always associated with a modernist aesthetic and thus appeared primarily in functional or environmental text (restaurant menus, signage, your business card, bloomingdales, etc.). It may be interesting to note that the inverse ALL CAPS style conveyed modernity in the last tech revolution (the evolution of the Microsoft logo, for example).
I was using all lowercase as my default for internet comments (and personal journal entries) for at least a solid decade, starting from some point in the 90s. I saw it as a way to take a step back from being pretentious.
I eventually ran into so much resistance and hate about it that I decided conforming to writing in a way that people aren't actively hostile to was a better approach to communicating my thoughts than getting hung up on an aesthetic choice.
Having started out as a counterculture type, that will always be in my blood, but I've relearned this lesson over and over again in many situations-- it's usually better to focus on clear communication and getting things done unless your non-standard format is a critical part of whatever message you're trying to send at the moment.
I'm a big fan of counter culture and so on, but generally the point of text is to be read and using all lower case just makes it harder for all your readers, which seems like the worst form of arrogance.
> [No-caps text] sort of grates on the ear for anyone over 35 [...] Incidentally, millenials also used the "no caps" style but mainly for "marginalia" (at most paragraph-length notes, observations)
I (a millenial) carried over the no-caps style from IRC (where IME it was and remains nearly universal) to ICQ to $CURRENT_IM_NETWORK, so for me TFA reads like a chat log (except I guess for the period at the end of each paragraph, that shouldn’t be there). Funnily enough, people older than me who started IMing later than me don’t usually follow this style—I suspect automatic capitalization on mobile phones is to blame.
> Additionally, The Chicago Manual of Style, which prescribes favoring non-standard capitalization of names in accordance with the bearer's strongly stated preference, notes "E. E. Cummings can be safely capitalized; it was one of his publishers, not he himself, who lowercased his name."[65]
The development of QM was so closely connected to experiments that it's highly unlikely, even despite some of the experiments having been performed prior to 1900.
I suspect the move back to pen-and-paper exams is being resisted by the teachers. It shouldn't be that hard though--when the workload became to great, most of my own professors would offload part of the grading task to TAs and grad students.
It does seem like in-person pen-and-paper exams would hold the line pretty firmly with respect to competence. It's a simple solution and I haven't heard any good arguments against it.
They really do want to know the ins-and-outs of the HVAC service business, for example, because they hope their agents will be handling it in a few years.
reply