StarTether (@StarTether) profile picture

LDS, software engineer, Ex-MSFT, PhD, opinions are my own.

Joined June 2012
Photo by StarTether (@StarTether)Photo by StarTether (@StarTether)Photo by StarTether (@StarTether)Photo by StarTether (@StarTether)Photo by StarTether (@StarTether)Photo by StarTether (@StarTether)Photo by StarTether (@StarTether)Photo by StarTether (@StarTether)Photo by StarTether (@StarTether)Photo by StarTether (@StarTether)
Every choice starts with this: Do you see others as equal to you? We all have an inner compass—call it conscience, spirit, or whatever—which we leverage when making that choice. 1/7
3
1
11
2,301
Fun fact: we use Zelda techniques to keep our cat happy. Progressively complex food dispensing devices. 6 pieces of Kibble scattered around the house each night in random, but consistent locations so she has to hunt. She begs for it, even though it's the same kibble in her bowl.
I beat Ocarina of Time as a kid without a strategy guide. Here are a couple of examples of how based on your examples: Phantom Ganon throws a giant ball at you. It hits you. Ow. He throws said giant ball at you again and you try hitting it with your sword, like you would a baseball with a bat, because why not? That works. Now you know. You figure out the Poes in the paintings by realizing they run when you get close and you've just conveniently been given a long-distance weapon (the bow). Its actually all very logical. There. Thats Zelda for you. If you get an item in a dungeon, you'll need to use it in that dungeon. Everything just takes a little thought. The problem nowadays is people don't have the patience. Handholding in games has gotten out of hand, IMO. Zelda is not random experimentation. You just need to use context clues the vast majority of the time.
3
258
I'm playing Ocarina of Time Remake rn and knowing how big of a tragedy it is has brought me to tears multiple times. Even Mido and Saria's relationship is tragic. And knowing this Link is the training Stalfos in Twilight Kingdom?! 😭Because of how the Kokiri Forest works. 😭😭😭
A lot of folks are talking about Ocarina of Time right now and many are rightly recognizing that it taps into older story telling forms than most games. I've seen quite a few calling it a fairy tale, and I want to clear up right now that those folks are wrong. At least in the Tolkienian sense. Tolkien's essay On Fairy Stories is required reading on the topic. In the conclusory pages, he insists that the happy ending is required in a fairy tale. And not mere consolation. A fairy tale requires a "sudden and miraculous grace." He coined the now famous term eucatastrophe to mean the opposite of a catastrophe. A sudden turn towards joy. This is the true ending of the fairy tale. (mild spoilers for OoT below) Ocarina of Time does have some of elements of a fairy story. Innocence. Wonder. But ultimately it's a multilayered tragedy. It's a game about loss. The innocent forest boy loses his childhood, slowly loses his companions, and then eventually loses his place in time as he is sent back to before it ever happens. And then he loses his fairy, which in the context of the game starting about the boy without a fairy, is a cruelest blow of all. There is no turn of grace for the hero, who carries the tragedy and memory with him. I can't map an exact literary structure onto Ocarina. It has elements of a heroic romance but is also more interested in myth making. But the tragedy also adds an 'Elegiac' element onto the story. It becomes something more similar in tone to the Arthurian Cycle, or Beowulf, where the story leaves you with a strong sense of what has been lost in spite of the heroism on display. Elegiac Myth? Not a recognized literary category, but that's what I would label Ocarina of Time. (Side note, not all Zelda games are this tragic, though several are. Link to the Past probably actually IS a fairy tale by the way, as it ends with every tear being wiped away and the healing of all harms.) (Also pictured below, additional scenes of loss and tragedy)
86
"As a rocket engineer, who designs rockets, Musk is probably replaceable. As a rocket company engineer, who designs rocket companies, he is not." Absolute gold.
A lot of people have real trouble thinking about the aggregate behavior of groups. They can only think about individuals. So they think about Elon Musk as an individual. Maybe they think that he must be retarded, because they need that for emotional reasons. Or maybe they think he is a talented rocket designer. But even if they realize he understands rockets, they can only think about him as an individual doing tasks. Not about his impact on what the whole company does. If Elon Musk is just a talented rocket designer, then he can spend all day, every day, improving rocket designs. But he is just one of 7000 engineers. So even if did a perfect job, he would only improve progress by about .014% So, when a midwit looks at SpaceX, he sees 7000 engineers, and says to himself "Elon Musk cannot possibly be designing the whole damn rocket himself. These people are giving him too much credit." This would be absolutely true if Musk were just a some random SpaceX engineer. But he isn't. He's the absolute dictator of the whole damn company. He decides, with absolute and unquestionable authority, which behaviors are punished and which are rewarded. Why is this important? When I worked at Boeing, on various classified projects, I naively came in with the assumption that I was a software engineer, employed to design and build functional software as quickly and cheaply as possible. Because of this, I focused on functionality and efficiency, for example suggesting changes that would obviate the need for entire projects and software components. And I very rapidly became persona non grata. At first, this caused me to adopt an air of aggrieved innocence. I was just trying to do my job well, and I was being punished for it. Then I gradually came to realize that I hadn't properly understood what my job was, or what the actual mission of Boeing Defense, Space, and Security was. Boeing DSS was not an aerospace company. Boeing DSS was a fraud company. Its goal was twofold. First, to maximize transfer of public tax dollars to stockholder pockets. Second, to maintain the appearance of being an aerospace company, to prevent the fraud from being exposed. Which meant that my real job was twofold. First, to generate billable hours. Second, to look busy. This is why Space Launch System sucks. Why it is always late when it doesn't fail outright. Why it is at 300% of its target budget. Why it leaves American astronauts stranded and needing a lift from SpaceX. That's because, for Boeing, building rockets is a side quest. Something they have to do to look busy. Yes, a rocket does occasionally fly, but that's just happening so programs don't get shut down. For Boeing, coming in early and under budget would actually be failure. The system is functioning exactly as designed. The cost, not the rocket, is the goal. Musk and SpaceX don't work like that. Unlike Boeing executives, Musk is not a useless grifter asshole. He is an entirely different kind of asshole... a rocket obsessed sperg. So, at SpaceX, engineers do not get rewarded for generating billable hours. They get rewarded for making rockets fly. And for all the subtasks of this, like figuring out how to make rockets lighter, figuring out how to make engines reignite better, figuring out how to make rocket exhaust not destroy launch pads, etc. And this attracts engineers who care about rockets. You've seen them on broadcasts, crying on open microphones because they dedicated their lives to something and it just flew. As a rocket engineer, who designs rockets, Musk is probably replaceable. As a rocket company engineer, who designs rocket companies, he is not. For over 50 years, the US space industry stagnated precisely for the lack of a Musk-like figure, who could not only create an effective aerospace company, but who could thereby demonstrate what an effective aerospace company looks like. Which makes it much more difficult for fraudsters to get away with fraud. I'm envious. I wish I could have worked for an aerospace company instead of a fraud company. But what's more important is that some of us now no longer have to play "who gets the most cheese?". They get to play "What can we build today?".
18
210
3
5,444
188,883
M365 failure comes from 3 issues: 1) latent deadlock bug 2) fail-over performed to test fail-over procedure. SOP. 3) 14% of machines in fail-over destination were out of service, causing load spike and triggering the deadlock. But the core is a deadlock they didn't detect.
More details on the root cause can be found in the Microsoft 365 Admin center, and an abridged version can be found below. We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations. The incident on Thursday, November 12th, 2026, was caused by three main factors that together caused a global outage for the networking gateway that fronts many Microsoft 365 services. First, a latent defect caused servers to become overwhelmed and unresponsive under certain load conditions. This was due to lock contention inside an internal process which caused the machine to become unavailable. This defect was the result of a fix that was prepared specifically for Microsoft 365 networking gateway servers; neither the underlying defect nor the fix applies to broader Windows deployments. The initial change in behavior first started deployment in July of this year. The update went through safe deployment and saturated globally over several weeks, during which time no issues were observed. For more than three months, the change was deployed worldwide without impact. Our normal load testing did not detect the latent issue because the different traffic and SKU mix used in our test labs. The contention issue is worsened on machines with more cores and newer hardware; whereas our load testing tended to focus on our weaker hardware SKUs with fewer cores. Second, a surge in load increased the likelihood for the networking gateways to encounter the contention. Within Microsoft 365, we maintain two independent and heterogenous network gateway systems designed for isolation and high availability. This allows many Microsoft 365 services to fail to/from them during outages or disruptions. Approximately fifteen hours before the outage, Teams failed over from the alternative networking gateway to the ‘primary’ gateway that also supports Exchange Online. This increased the load on the networking gateway and changed its traffic patterns. This type of failover is part of normal operations and is integral to standard Microsoft resiliency efforts. Third, at the same time, nearly 14% of server capacity for the networking gateway was out of service due to an unrelated issue from the previous day. This server capacity was on track to be returned to active service through routine maintenance and health processes. The service had sufficient capacity headroom, so the reduction in server capacity had no impact on its own. Taken together, the increased load and the reduced server capacity, caused the network gateway to encounter the latent bug from July. This caused requests to build up until servers ultimately stopped responding. This occurred during the peak window of traffic in the United States. When servers lose connectivity, our traffic management systems automatically route users to other healthy endpoints. This happens often and is critical to avoiding any interruption due to hardware, software, or network defects and is normally what makes the service resilient. However, the redirected traffic increased the likelihood for the same problem to occur on the remaining endpoints. This caused a cascading failure from server to server as the same amount of load was spread across fewer servers. In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive. At its lowest, more than 80% of servers were unresponsive. Normally, the network gateway is composed of thousands of ‘capacity units’ which represent shards of capacity, hardware, and networking infrastructure. These ‘capacity units’ are then organized into regions. In this case, due to a separate issue, the normal bulkheads between these different partitions did not stop the cascading failure. This is what allowed the impact to spread across our network gateway infrastructure globally. Several services like Teams, OneDrive, SharePoint, and Office apps failed out of the faulty network gateway infrastructure. That is why those services were restored earlier, with Teams chats and meetings functioning without issue for most of the outage. But not all services, like Exchange Online, can fail out of this network gateway. Recovery took longer than usual because as servers returned to service, they were immediately overwhelmed by waiting traffic and became unresponsive again. Our normally automated recovery processes were not designed to restore service from this broad unresponsive state. Additionally, since the main code defect was a latent bug from several months previous, our normal rollback, flighting, and feature flags were unable to quickly revert the change. After engineers confirmed the defect as the cause, we developed an update that returned the code path to the previously known good state. To effectively apply this fix, and to slowly bring the service online again, we took groups of servers out of service, applied the change, and restarted them before returning them to service. This process was carefully applied to large quantities of infrastructure at a time (e.g. 50%+ of a region). The final Post-Incident Review (PIR) will provide more details later this week.
73
I played this one start to finish so many times, I can't count them. I wanted a full play without ever dying. I don't think I ever accomplished that. Stupid Moldorm...
>only 3rd entry in the series, 2nd traditional style >released 1991, basically prehistoric >basic game loop throughly refined to perfection in a way no entry would ever come close to at all >still the best entry by far despite the big inherent limitations How did they do it bros
4
132
THIS RIGHT HERE is why I-001 was so important…. The culture of secrecy sanctioned by the Legislature will be even worse after the WEA teachers union spent millions defeat I-001 and to shut parents out. Olympia’s shutting parents out is absolutely at the root of this terrible and gross activity the school counselor seemed to think was OK. This is a 14 minute video. You should watch it the whole damn thing. Get informed. I-001 may have lost but the problem is still very real.
📍🚨 SHELTON, WA - School counselor caught in the woods with a 15-year-old wearing booty shorts. I think the parents need to be questioned as well.
19
90
3
303
7,083
StarTether retweeted
Cops just called. Asked about my recent X posts. Told them to get a warrant! My lawyer is involved Then a man claiming to be a bishop called me. Said he used to be in the CIA and he was going to make me pay! This is surreal. I've been crying for an hour now. Stomach ache. Nausea. I've thrown up twice. I have no idea what this is about! 😢😭😮‍💨🤮☠️☠️☠️
22
6
3
275
20,369
StarTether retweeted
I hear the FAA had to issue a ground stop because their systems all use WinRAR, but they keep the registration key in Outlook.
46
70
4
1,171
39,947
24
87
6
483
7,159
StarTether retweeted
Microsoft was down for most of 18 hours. Here's the part nobody is telling your boss. Microsoft promises 99.9% uptime a month. In November that's 43 minutes. Down more than 43 minutes: 25% off the month. More than 7.2 hours: 50% off. More than 36 hours: the month is free. It isn't automatic. Your IT team has to file a claim.
9
40
236
11,305
StarTether retweeted
Somewhat happy to say I am no longer responsible for the worst Outlook outage (26 years ago)
24
26
2
406
18,722
StarTether retweeted
Super glad I'm no longer on the Microsoft PR team.
11
1
1
78
5,346
StarTether retweeted
698
2,454
493
28,189
748,866
Since apparently we can post up to 20 photos/videos now here are a bunch of mine
910
3,088
280
25,773
888,136
StarTether retweeted
Whooops. Tyler thought: "No em dash, I'm in the clear!"
7
9
149
7,066
Reappropriating Arthur C. Clarke
Replying to @UsingLyft
Any sufficiently advanced stupidity is indistinguishable from malice.
2
84
StarTether retweeted
We also have centuries of data suggesting that making murder illegal doesn't make it go away. Should we legalize murder and focus more on investing in rage rooms and social workers?
It doesn't work dude. *It does not work*. We have DECADES, potentially CENTURIES of data that say restricting abortions does not make them go away.
11
5
1
98
2,702
StarTether retweeted
Texas is an interesting case. The Democrats haven't even taken control following the elections and they've already got 20 gun control bills ready to go. The governor-elect says she'll sign them. (The TX Senate is GOP so these bills are going nowhere.) I thought the midterms were about affordability? Gas prices? My prediction, and it applies nationwide and not just in Texas: the Democrats are going to MASSIVELY overplay their hand. They can't help it.
183
227
14
4,026
86,835
Responsiveness is rarely considered during development because developer time is the most expensive in the moment. Devs are given the fast devices so they can iterate and build quickly. Their ux is below the Dorothy Threshold for them, and if it isn't, it's close enough. 1/
UX latency is the most frustrating (lack of) advancement in computing over the last ~50 years. IBM, way back in the 80s, found that user productivity shot up *exponentially* as system response time dropped. The "Doherty Threshold" was defined as ~400 milliseconds; the maximum amount of tolerable UX latency before interrupting user flow state. It's unbelievable how many modern operating systems (*cough* win11) violate this threshold constantly. Literally all you need to do as a Dev is pay attention. Add a "Doherty Threshold" to your test suite. There's so many different profiling tools, and especially with how good models are, really no excuse. Sure, some stalls are unavoidable, but that's when you pull out other UX tricks to at least give the illusion of responsiveness. Crazy how much vintage computing hardware feels immeasurably more responsive despite having thousands of times less overall performance.
1
49
I'm not excusing, here. Just explaining. Getting automation into the loop to make the latency visible and forcing devs to consider it is the tough part. Their goal is getting the feature to work, first. Everything else is considered gravy to them. /2
7