I have every sympathy for the folks who lost homes here in California last year; it could easily have been my house. But what a lot of discussions miss regarding SCE's role in the Altadena fire is that SCE is a public utility, and California's Public Utilities Commission has not been allowing SCE (or other utilities, like PG&E) to charge rates that would allow them to do the required maintenance to prevent fires. In another case, some years ago, I understand that a fire in Northern California started next to a PG&E substation; the brush had not been trimmed, so I'm told, because environmental regulation didn't allow it.
From where I sit, this is not simply a "power company bad" situation; the state has played a significant role.
The problem here isn’t the rewrite, the problem here is toxic management, massive feature creep, unrealistic expectations, etc., etc. You’d have been doomed without the rewrite.
This is one of those perennial ideas; let's get rid of hierarchical file systems and just keep all the files in a database. Speaking as a user who knows how to keep things organized, I like hierarchical file systems. Store the data in a database if you like, but don't break my metaphor.
The TCL community experimented with an idea like this many years ago; they were called "structured documents" or "starpacks". What we found was that (A) it's usually more convenient to keep the data in a separate file, and (B) virus checkers can get suspicious when your app starts modifying itself, leading to unintentional comedy in operations. YMMV.
Young Americans have been fed a constant diet of “the Modern World is Awful” and “You Are Doomed” for quite some time now. This is just the next round, and as always it is overstated.
I'd not seen the spelling "sike" until today; but I've been spelling it "psych" since I was in grade school in the early 70's. Definitely derives from "psyching someone out", i.e., confusing them or tricking them (in that I first heard "psych" as shorthand for "psych out"). I wouldn't be at all surprised if it's older than that.
The ecosystem makes it feasible to use the language or not. For my personal projects, I won't use a language that doesn't provide some kind of straightforward cross-platform GUI toolkit (nearly) out of the box—which narrows the field enormously.
But it's the syntax and semantics what determine whether I'd want to use the language to begin with, and how maintainable the resulting code is.
I had at least one Gateway 2000 desktop and several laptops over time. All but the last laptop were lovely machines. The last looked good on paper, but it was thicker and heavier than it should have been, and start losing keycaps fairly quickly.
Using `switch` is not a better approach if the design allows for outsiders to add their own shapes at a later time. Using `switch` probably is a better approach if the range is shapes is fixed and new shapes can't be added, especially if the language's `switch` statement requires that all valid cases be included.
Using the proleptic Gregorian calendar for historical dates is only a problem if you want to compute the day of the week (which those missing days will throw off prior to the adoption of the Gregorian calendar in the relevant country) or the number of days between two historical dates (if the two dates span the date when the Gregorian calendar was adopted).
And, frankly, there are other problems to deal with beyond correctly handling the Julian/Gregorian switch. In Nelson's Navy, for example, the new day started at noon rather than midnight as we'd expect. AM could be June 1st, PM could be June 2nd, and both could be Tuesday.
And then there are lots of historical events with dates like "on or about August 6th" or "mid-September" or the "in the Fall of".
Trying to deal with historical dates in what a programmer would consider a perfectly correct way is something of a fool's game.
I stopped reading Eddings because after a while I realized that all of these fun, bantering characters I so enjoyed were (except for Garion, mostly) truly awful people and that I didn't want to spend any more time with them. That was after I'd re-read them many times, and long before any revelations about the author. (Really, Polgara? Your reaction to being balked is to smash everything in sight? You haven't matured at all in your vastly long life?)
As for MZB, I agree completely. No desire at all.
WRT to O'Brian, though--it's clear, as the OP notes, that he knew his faults, recognizes them in his characters, particularly Maturin, and shows them for what they are. To put it another way, his faults don't "poison" his books from within.
The loss of 3rd places is a big deal; but it seems weird to wax nostalgic over the remarkably brief period that movie rental stores were actually a thing. Blockbuster Video opened in 1985, was overtaken by Netflix starting in 2000, and died in 2010. There were small movie rental shops prior to 1985, but not long prior.
I was exposed to Z notation in the late 80's, and could not for the life of me see how to apply to my work as a junior programmer. But the distinction the OP makes between Design and Code Specification was lost on me then (and, I think, on the folks I knew who were looking at Z); and the OP indicates that Z is aimed at Design Specification. As a junior programmer, it's no wonder it was lost on me.
I'm mostly a solo programmer, and I often have to go back and look at code I wrote five, ten, twenty years ago. And every time I do, I give thanks that I used comments to document my intent. My memory's good, but it's not that good.
Re: Mr. Martin's agreement, whether he agrees or not is not nearly as important as the impression his book gives and whether your "Clean Code"-reading co-workers agree. I know people who genuinely try to get rid of all comments as "Clean Code" suggests, and I'm glad I don't need to maintain their code.
On the contrary, language code is what is "authored". The authoring tools are the IDEs, editors, compilers, etc. that we use to produce the executable application.
At least not automatically. From an algorithmic standpoint it seems likely to be undecidable. But let us not look too closely at what was really a throwaway remark.
A stated goal of the API is to have "low ceremony" when reading arbitrary JSON files. I agree the JSON creation API looks pretty clunky, but the parsing API looks fairly simple.
Fascinating. When I was a kid and was having difficulty with some task, my grandfather would say, "You didn't hold your mouth right." Many years later, I realized that he was talking about tacit knowledge (and probably most specifically about one's embouchure when playing a wind instrument). There are vital aspects to most skills that are simply not evident to the casual observer.
I had not heard the phrase "tacit knowledge" until today; I'm glad to have a word for it.
Re: Java classes called "SimpleFoo": that's usually because `Foo` is an abstract class or interface, and `SimpleFoo` is the version you actually use most of the time, unless you absolutely have to implement a `MyReallyComplexFoo` for some specific purpose.
I remember the golden age of dial-up Bulletin Board Systems. I remember the golden age of Usenet. I remember the golden age of blogs. I remember the golden--well, silver--age of FaceBook and Twitter.
Things tarnish. New things pop up to replace them. I'm currently witnessing the tarnishing of Substack.