2024-12-03
7 分钟Alex Russell answers the question, "If not React, then what?" Csaba Okrona identifies four core problems that create and reinforce knowledge silos, Rob Koch's Markwhen is like Markdown for timelines, Jeff Geerling is quite impressed by Apple's latest iteration on the Mac mini & Sylvain Kerkour took the time to draw a comparison of Amazon's O.G. S3 service with Cloudflare's R2 competitor.
What up nerds?
I'm Jared and this is Changelog News for the week of Monday, December 2, 2024.
We've arrived at months sub 11, which means everyone's breaking out their year end content.
First up, Oxford, you know the dictionary.
They've selected their word of the year, brain rot, which is a noun supposed deterioration of a person's mental or intellect state, especially viewed as a result of overconsumption of material, particularly online content considered to be trivial or unchallenging.
Hopefully we do not contribute to brain rot.
But speaking of year end content, we are preparing for our seventh annual State of the Log episode and we need your help.
Please go to Change Log FM sotl, that's short for State of the Log and leave us a voicemail.
If your audio is used on the show, we'll hook you up with your very own Breakmaster Cylinder Remix.
Okay, let's get into this week's news.
If not, React, then what?
In the hopes of steering the next team away from the rocks, Alex Russell dives deep on why he believes nobody should start a new project in the 2020s based on React full stop.
His overarching message Quote Frameworkism isn't delivering the answer isn't a different tool, it's the courage to do engineering, end quote.
I've been preaching similar things around these parts basically forever.
Not against frameworks per se, but against the belief that the next framework will deliver us from whatever self constructed hellscape of a code base we are currently abiding in.
This statement by Alex rings particularly true.
Quote A shocking fraction of decent, well meaning product managers and engineers haven't thought through the whys and wherefores of their architectures, opting instead to go with what's popular in a sort of responsibility fire brigade.
The real cost of Knowledge Silos Casaba Okrana takes note that the Stack overflow survey revealed 45% of developers hit knowledge silos three or more times per week.
Here's what keeps him up at night 1 engineers feeling frustrated and isolated 2 innovation dying in departmental dead ends and 3 your best people solving the same problems over and over.
After years of scaling engineering teams, he has identified four core problems that create and reinforce knowledge silos.