> In my experience, managers enforce code review as a quality control mechanism: the "Find Bugs" step in the article's pyramid.
Nope.
To reduce it down to a single word, I'd say we do code-reviews to assess "taste".
-----
Code-review is one part of a larger process (the SDLC!), and while review does help with "finding bugs" it is not the singular reason why we do it; and other parts of the SDLC are concerned with finding bugs in the first place, namely the various Test and QA steps in the process; when your code is in the (peer) code-review step then there's an expectation that the author already identified and resolved actual bugs/defects (i.e. where actual-program-behaviour deviates from the spec[1]), so a PR for new functionality is expected to include unit and integration tests to demonstrate that.
Now Claude will gladly take a Jira ticket, write-up a plan/spec, write tests, implement the feature, verify the tests pass, address static-analysis issues, push branch, and submit the PR - and if-the-program-works then it's "correct" and so surely there's nothing really to review and so merging the changes should be a breeze... but I find myself rejecting these PRs all the time because these agents still "just don't get it"[2]. (But I'm sure they'll "get it" eventually; you can't stop progress). We can revisit this topic when we get there; but for now I'm going to reject an AI-authored PR that eschews it.
Good taste is important.
[1] I'm not going to pretend anyone actually writes any kind of spec (informal or otherwise) for the vast majority of software out there; but an unwritten-spec exists when you mentally combine a vague Jira ticket, platform-conventions and common-sense (and that's how Claude in an Agentic Loop works too, except it always has to write-out the Spec.md/Plan.md to disk first, whereas us humans keep things in our head).
> Redux only plays a role in adding syntactic sugar over React's support for reactive programming
Redux doesn't have anything to do with any kind of syntactic-sugar for Reac.
> the general guidelines are that you should only bother with Redux if your SPA is already considerably complex
If one already has an (non-React) SPA which is not already built following Redux then you're stuck with what you've got; it isn't really possible to take an existing SPA of any complexity and deciding to "make it use Redux" because it completely up-ends practically every aspect of SPA application-design, at least as far as how "traditional" (non-React) SPAs do things.
If you'll permit me to oversimplify: I tell people that React is a basically an opinionated Redux kernel wrapped around a JSX-based DOM+component/widget system (, which then means you now need a JS build system too); or conversely: Redux is like React, except without JSX components.
> the ones people complain about and the ones nobody uses
The funny thing is that prior to 2015 "the ones nobody uses" were the academically-designed ivory tower FP languages; perpetually relegated to being a minority curiosity because FP is immensely difficult to wrap one's head around at first, especially if all you've-ever-known was imperative C or VB and (compromised) OOP in Java and C#.
I remember when Google's overqualified design-team for Angular decided that Angular2+ is too good for Promise-based fetch() - instead everyone should be forced to learn RxJS's way-of-doing-things - cue the agony, wailing and the gnashing of teeth.
...I think being forced to live through that experience did 2 things:
1) It forced an entire generation of front-end web-devs (and VB6 refugees) to get familiar with FP-like concepts.
2) It also made those same front-end web-devs swear-off ever using a Google-maintained SPA framework in future.
...which set the stage for the mass-adoption of ReactJS:
1) It made effective use of FP concepts, which many devs were now accustomed-to after having survived Angular2.
Credit where credit is due, though: ReactJS became #1 on its merits.
...yes, Redux (not React) deserves to be #1, but Redux isn't a complete, all-under-one-roof framework the way React is; but regardless of that: The Redux/React approach is just fundamentally a better design than what we had before: stateful-controls/widgets and two-way data-binding.
If you'd like to relive how UI devs suffered throughout the 1990s, 2000s, and most of the 2010s I invite you to try making a native Windows 11 desktop UI using WinUI3 using the MVVM (anti-) pattern: nothing but mutable objects of indeterminable state getting caught in infinite-loops or unbound recursion due to INotifyPropertyChanged - and Microsoft is still pretending that's the "right" way to build a UI.
Sorry am ranting on about something I have very little control over; it's just frustating.
> if your purpose is truly to learn or to teach, the process of describing that image will do wonders for retention.
If you're wanting to learn then you won't have the expertise to craft a prompt that has the correct details or to spot when the model makes a mistake in its output.
If you're in a teaching position then you won't have anything to learn.
…but the illustrative diagrams are a simulacrum; if you ask Qwen, or any image-generator, for an “accurate” poster-design featuring a representation of a model of an atom and explaining its constituent parts I expect you’ll get an imitation-airbrush rendering of red, blue, and grey table-tennis balls orbiting in perfect circles; you might get an electron-shell diagram if you’re lucky. What you won’t get is anything remotely related to probability-clouds.
Edit: just to test myself I asked Nano Banana 2 to generate “an undergraduate infographic poster about how atoms work” - and the result was something right out of a middle-school science textbook and very Bohr…
With a GPU ban, then the PRC will accelerate domestic "AI chip" R&D and production, while still getting-away with grey-market imports for their AI/LLM R&D.
Without a GPU ban, then the PRC will accelerate domestic AI/LLM R&D and deployment, while still funding indigenous AI chip development efforts.
------
From afar it makes America look so insecure and almost pathetic: China's R&D ecosystem is a huge mass with a lot of inertia - trade policy and embargos will be about as effective against it as the paper they're printed on.
> how many current persons working on Minecraft are also Modders?
Probably less than you'd think: lots of people recognise they need to leave their work behind at work and not get too emotionally invested in something they love, because at work they'll be exposed to the gut-wrenching business-decision sausage factory.
> “When people first saw it, they said, ‘Why haven’t we been doing this for a hundred years?’” Doerr said. “That’s the kind of question I love to hear, because it means the culture of safety innovation is alive and well.”
Union Pacific haven’t been doing this precisely because they don’t have a culture of innovation…
> I don't want people to lose jobs. I don't want the advantages to accrue to a few hyperscalers.
Versus:
> It is now possible for dedicated, hard-working ICs in several domains to produce extremely good products in a short amount of time without external capital and without studio meddling
A contradiction exists: lower-capital requirements means less employment all-around and more profit to fewer people.
“Anchor + Offset” is stable because the anchor param should uniquely identify a specific record from which the offset is applied; a sort-order, direction, and page-size may also be optimally specified.
I think they meant how you can’t get a permalink to your feed/timeline view-state[1], so other people can see exactly what you see (not just what’s in the viewport but also the surrounding/offscreen content and broader context).
[1]: something like a link specifying the contents of my feed at a specific date+time and scroll-position.
…whereas with old-school SSR paging it’s right there in the querystring paging params (page-size, page-index or item-offset, and an optional results anchor for stability).
I’ll concede that a well-designed infinite-scrolling (or “click to load more inline” button) feature could use history.pushState to dynamically update the browser’s address with new query params but I don’t think I’ve ever actually seen anyone do that - which is a shame.
I imagine their internal culture/aesthetic is where their FDEs don’t have projects, they have “missions”; they maintain a “kill-chain” instead of a pipeline, they will attack a problem - solving problems sounds like math homework; and everyone from leftist idealists, concerned citizens and industry competitors are all “the enemy”.
There's no conspiracy here; the UK government is not wanting to censor Wikipedia (honestly!) - what this really is is the consequence of poorly written legislation introduced at the behest of tabloid-newspaper-supported children's online safety nonprofits - they have a very high level of public support (from parents stressed-out over how bad the Internet is thesedays, which is fair enough!) - and this translates into strong political support, which leads to MPs actively avoiding listening to technical experts and other opposition voices because no-one wants the Daily Express to call them out as being on the side of (vague and nebulous) Internet child sex predators (or "the paedos" for short, in UK tabloid speak).
...and none of this has anything to do with Prince Andrew et al (because that's in real-life, not on the Internet).
It's the exact same process that lead to the 2010s IWF/Cleanfeed/Wikipedia block over controversial 1970s music album art.
It's idiocy and fear of a rabid public, not a conspiracy.