VeryStableProgrammer (@stablegeniuspro) header
VeryStableProgrammer (@stablegeniuspro) profile picture

came for tech tips now posting into the void

United States
Joined August 2024
Photo by VeryStableProgrammer (@stablegeniuspro)Photo by VeryStableProgrammer (@stablegeniuspro)Photo by VeryStableProgrammer (@stablegeniuspro)Photo by VeryStableProgrammer (@stablegeniuspro)Photo by VeryStableProgrammer (@stablegeniuspro)Photo by VeryStableProgrammer (@stablegeniuspro)Photo by VeryStableProgrammer (@stablegeniuspro)Photo by VeryStableProgrammer (@stablegeniuspro)Photo by VeryStableProgrammer (@stablegeniuspro)Photo by VeryStableProgrammer (@stablegeniuspro)
The human brain is optimized for tabular forms. You can try to escape it, but won’t. Data are relations. No-SQL is an affront to God and nature.
Satya Nadella on why Microsoft Excel has been so durable after 40 years: > the power of lists and tables > the malleability of the software (“a blinking canvas”) > spreadsheet software is Turing complete (“I can make it do everything”) > it’s the world’s most approachable programming environment (“you get into it without even thinking your programming”)
1
31
8,077
If you communicate with AI tools in any tone you are a goy and ngmi
1
36
Vance getting thrown out for Brandon Gill is an all-timer for the ‘at 40 it’s over’ maxim.
8
SO TRUE
JUST IN: President Trump declares he’s not concerned about the recent string of major outages — “It’s life.”
1
120
This goes so hard
you arent pulling any bitches because your dating app pics look nothing like this
1
71
How it feels to demolish 10 lumpia for $5.99
Trump arrives in the Philippines.
1
1
165
Let them cook
JUST IN: Variety names Hunter Schafer to its Bond girl “wish list” for Robert Pattinson’s 007 debut.
14
This guy was a literal Never Trumper who said he didn’t vote in 2016 and would let Hillary Clinton win.
NEW: Ben Shapiro is LOSING IT over Nick Fuentes' speech this weekend. He even plays short clips of it on his show.
25
VeryStableProgrammer retweeted
We’ve come a long way
2,335
7,034
317
99,979
4,066,699
Everyone knows I am right that Robert Pattinson should dump Kristen Stewart. In a couple of years, he will thank me. Be smart, Robert.
3
572
Jensen the White is coming!
BREAKING: Jensen Huang is considering returning to Nvidia, $NVDA, as CEO as tech executives pressure the company’s board to reinstate him, per FT. Huang is reportedly discussing a potential return even as an independent investigation by Nvidia's board is underway. One "ally" of Jensen Huang is reportedly putting together a "war room" of tech executives to lobby for his return. It's going to be an interesting week to say the least.
58
950
42
13,204
266,547
Very true
Elon haters be like: “Michelangelo wasn’t a great sculptor. He just removed the parts of the marble that weren’t David”
1
53
It’s over
Florence Pugh attends the 17th Governors Awards.
14
Why does he look like the Indian Ron Jeremy now?
New York City Mayor Zohran Mamdani disbands the NYPD’s 600-officer Strategic Response Group, responsible for riots, mass protests and counterterrorism. Beginning in January, protest response will shift to a civilian-led de-escalation division supported by just 30 officers, with restrictions on pepper spray, tear gas and long guns. Follow: @AFpost
1
118
You can connect your phone to your car and you can talk to your car while driving and a 145 IQ virtual assistant can perform almost any digital task for you.
I have been so down lately, coupled with being exhausted. I don't like this world. I want the 90's, the 80's .... even 70's. The decade is horrible,.
2
86
VeryStableProgrammer retweeted
Cron jobs → Autonomous Agents APIs → MCP Servers Database search → RAG Vector databases → Long-term Memory If/else statements → AI Guardrails Web scraping → Deep Research Put an LLM somewhere in the middle and suddenly it's a $50M startup 😭
AI mfs basically rebranded cron jobs as autonomous agents😭
44
443
35
3,710
85,932
“14% of server capacity offline for an unrelated issue, not great not terrible”
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.
2
76
Jensen Huang is coming back at the dawn of the fifth day to annihilate your short btw
1
48
If you haven’t been blocked by Harmeet Dhillon at this point you have terrible political instincts or you’re super liberal.
Hey Harmeet, given that you hate white nationalism so much, can you clarify who the “we” refers to in all your posts concerning India and Indian nationalism?
1
7
186
“This 2027 governors map was because of the Texas railroad commissioner..”
You were a ball and chain wrapped around the necks on the GOP in Texas. You can take credit for the worst GOP losses in TX for decades. We don’t do hierarchies of Americans.
38
Hey Harmeet, given that you hate white nationalism so much, can you clarify who the “we” refers to in all your posts concerning India and Indian nationalism?
unavailable
3
1
13
739