Not quite the same thing, but there's this incredible (open source) project called The Component Gallery that is basically just a repository of UI components across 93 (currently) different design systems. It's an incredible resource if you're building a component from scratch and either want some design inspo or technical advice. Many of the design systems have thorough guidelines for a11y/ARIA best practices that I've learned a ton from
I strongly recommend watching/reading the entire report, or the summary by Sal Mercogliano of What's Going On In Shipping [0].
Yes, the loose wire was the immediate cause, but there was far more going wrong here. For example:
- The transformer switchover was set to manual rather than automatic, so it didn't automatically fail over to the backup transformer.
- The crew did not routinely train transformer switchover procedures.
- The two generators were both using a single non-redundant fuel pump (which was never intended to supply fuel to the generators!), which did not automatically restart after power was restored.
- The main engine automatically shut down when the primary coolant pump lost power, rather than using an emergency water supply or letting it overheat.
- The backup generator did not come online in time.
It's a classic Swiss Cheese model. A lot of things had to go wrong for this accident to happen. Focusing on that one wire isn't going to solve all the other issues. Wires, just like all other parts, will occasionally fail. One wire failure should never have caused an incident of this magnitude. Sure, there should probably be slightly better procedures for checking the wiring, but next time it'll be a failed sensor, actuator, or controller board.
If we don't focus on providing and ensuring a defense-in-depth, we will sooner or later see another incident like this.
>Sidekiq withdrew its $250,000/year sponsorship for Ruby Central
Whoa! I'm blown away that Sidekiq has enough money in the bank that one of their sponsorships is $250k/yr!
Sidekiq the company (actually ContribSys) is just one guy: Mike Perham.[0]
I listened to an interview with Mike a few years ago, and he seemed like he had an amazing setup. He was making about $1M/yr with no employees, just him selling code and contributing to open-source. I don't think he even has servers to keep online.
According to this podcast from 2023, he's now making close to $10M/yr in revenue and is still just running the whole thing by himself.[0] Great life for a solo dev founder!
On the other hand, many things attributed to chance are actually the aggregate effect of other people's choices. If we make choices based on not just what's best for ourselves but what's best for all of us, we will all suddenly become more "lucky". And vice versa, if we only think about ourselves that luck will diminish.
> Initially, the AI’s designs seemed outlandish. “The outputs that the thing was giving us were really not comprehensible by people,” Adhikari said. “They were too complicated, and they looked like alien things or AI things. Just nothing that a human being would make, because it had no sense of symmetry, beauty, anything. It was just a mess.”
This description reminds me of NASA’s evolved antennae from a couple of decades ago. It was created by genetic algorithms:
Based on this open source project, modders have created an expanded universe encapsulating RA, RA2, Tiberian Sun, Tiberian Dawn and other lore into Combined Arms mod:
This debate is extremely dumb, and everybody gish gallops and implies something terrible when they try to explain what Automattic is doing wrong, because they can't figure it out. So they instead give reasons why they insist it will be bad for his business (isn't that his business?) and pretend like that's him "technically" not doing anything tortious. It's not technical, the lawsuit from WPE is there to read. It's silly, and if it's not thrown out it will be because the judge needs time to understand the complexities of the license (and the promise that "Wordpress" will be turned over to the community after Automattic, who has an exclusive license to the trademark, shuts down.)
Using the reasons that you think this is a bad business decision as proxy reasons why he's wronged everyone making a living from his work is a veiled threat. Don't threaten to leave, just leave.
Maybe the problem is this haunting by the "Spirit of Open Source" where people insist that they have all of these rights that aren't in the license. Wordpress is not open source. It is Free Software. You already own it. Fork it if you want. If WPEngine is already doing almost as much business as Wordpress.com, they can handle everything themselves. If people love WPEngine more, they can leave. Don't whine when the value proposition for WPEngine changes after they have to take care of everything themselves, and they start violating the Spirit of Open Source until their bottom line looks better again.
I'm swearing an oath to violate the Spirit of Open Source wherever I see a hint of it, I'm just sticking to the licenses. The Spirit of Open Source somehow makes already wealthy people feel entitled to everything in the world. Free Software is important to me, and the people who make it should be as aggressive as will financially benefit them, as long as they abide by the letter of the GPL. The software is what's important, not that your half-billion dollar business is built on top of somebody else's half-billion dollar business. That's a you-problem.
Also, this is just straight up abuser behavior towards this guy. He doesn't do what you want with what is his, so you degrade him and accuse him of stealing his own property. It's hard to watch.
I'm going to stop commenting on these threads, but this mobbing is ridiculous. I hope he's emotionally stable; but a lot of tech CEOs aren't, and his awkward reactions to the pitchforks don't give me confidence. If you're compulsively reading all of these threads, stop now. Stay strong and know that 95% of this is coming from people who are directly connected to this financially and just don't want to be inconvenienced.
We face a number of challenges simply letting our paying customers change their search engine:
1. On iOS the list of allowed search engines is simply baked into OS, we have a fiddly extension that hooks outbound calls to /search and redirects them but I wish we didn't need to.
2. On Chrome, we use an extension to change the default search engine and enable search auto-complete etc, but Google has a policy that such an extension can do one thing and one thing only, and recently removed our extension on account of that [1]. We rebuilt it to meet their needs but had a lot of back-and-forth because we included 'search by image' on a context menu item and the first reviewer felt that was a bridge too far. You'll note that Chrome provides such a context menu item for Google Image search out of the box.
3. On Chrome for Linux, the default search engine API is not available, so Linux users have to configure it manually through a series of silly steps [2]. This is at least in keeping with most Linux experiences.
There are other issues, but I say all this to highlight how surprisingly difficult it is to change this setting in a practical, consumer friendly way. It is most certainly this difficult by design, that's a lot of revenue to protect.
Neal Stephenson explored international internet infrastructure in other works as well:
Reamde (2011) involves the hijacking of an undersea fiber-optic cable and the resulting disruption of internet connectivity in various parts of the world.
Interface (1994) involves a corrupt presidential candidate who seeks to control the internet through the manipulation of network infrastructure
“Blind Man's Bluff: The Untold Story of American Submarine Espionage” - Sherry Sontag & Christopher Drew - Indirect, but the title is the summary. I recommend familiarizing yourself with Operation Ivy Bells.
Ivy Bells is arguably the Cold War’s signature known clandestine undersea cable tapping operation. Contextualizes lengths nations will go to for physical access. It is far easier to own a cable than use a nuclear powered sub to sneakily deploy a tap.
I found the book maybe a bit overly optimistic/idealistic about how he thought infrastructure dependencies would impact the world, but a lot of the information was fascinating nonetheless.
This is how I move fast and break nothing. By having fullstack type-safety from database all the way to the frontend with auto-completion. My current stack:
+ SvelteKit (could be Next, Nuxt, Solid or any other TypeScript framework)
+ tRPC (typed calls between frontend and backend, https://trpc.io)
https://learn.microsoft.com/en-us/azure/architecture/pattern...