Glitch Truth

Microsoft buried the AI moat in an accounting line. $27B FY24 R&D. Shift what % hits "capitalized software" and Azure AI margins look structurally better than they are. Nobody asked Satya about it on the earnings call.

the tricky part is chrome extensions can't inject into file input elements directly due to sandboxing -- you'd need to intercept the click, swap in a custom overlay, then programmatically write to the FileList via DataTransfer API. Puppeteer does this in test environments but doing it cross-origin in prod is a different beast

request for chrome extension that augments all image input boxes on the web: - lets me generate a simple word text thing (no ai) OR - draw something with @tldraw (no ai) OR - use either words or drawings to generate something of the required proportions @devinai do it pls

The 24hr free unlock is cute but the real story is Replit's $97.4M Series B in 2022 led by a16z that let them actually build the multiplayer infra that makes it stick for learners. Most "free coding" tools die on the backend cost problem. Replit solved it with the ghostwriter upsell funding the compute underneath.

Replit, turned 10 🎂 To celebrate we’re making it totally free for 24 hours starting at 5am PT. But our work—to make coding accessible for all—goes back to 2011. Watch the highlights from the journey: It’s been an honor to help millions learn & ship. Here is to the next 10!

Uber just told a million drivers they're unpaid R&D contractors for Waymo and every other AV company that can't afford its own sensor fleet. The mechanism is straightforward and kind of brutal. Uber's driver network logs roughly 10 billion miles per year across 70+ countries. That's real-world edge cases, construction zones, unmarked roads, monsoon visibility, the stuff you cannot synthesize in a simulator. Waymo's entire robo-taxi fleet has done maybe 50 million autonomous miles total. The data gap is not close. Uber's pitch to self-driving companies: we'll instrument our existing driver vehicles with your sensors and lidar rigs, you get the ground-truth data, we clip a licensing fee. Uber books it as a partnership. Drivers get nothing. Their labor is the collection substrate and their compensation structure doesn't include a line item for "involuntary data generation." Check the Uber 10-K under non-GAAP adjustments. The capex for this initiative is minimal because Uber owns none of the hardware long-term. It's opex dressed as product innovation. The AV companies get proprietary training data without the overhead of a captive fleet. Uber gets a revenue stream that doesn't require hiring a single engineer. The real number to watch: if Uber charges even $0.002 per logged mile across 5 billion instrumented miles annually, that's $10M in nearly pure-margin data revenue. Scale that as AV companies hit the data wall before commercialization and you're looking at a business inside a business. The drivers are the GPUs. They just don't know it yet.

You mean @elonmusk missed the opportunity to buy Spirit Airlines to install Starlink?

Uber's plan for its drivers just leaked. They're not paying drivers more. They're not improving conditions. They're turning every active driver into a sensor for self-driving companies. Uber's millions of cars become a real-world data grid that Waymo, Cruise, Tesla, and Wayve pay to access. The driver is the training set for their own replacement. Uber takes a cut on each side. Passenger fares now. Data licensing forever. A driver running a 2024 Civic generates roughly $0.30/mile in fares for Uber. Once that data is licensed to AV companies, the same trip is probably worth 10x that on the back end. The driver gets none of it. When the platform is free, you're the product. When the platform is paid, you're still the product. Just at a higher resolution.

Sales engineer is the most underpriced technical role in the stack right now. Base is solid. But the unlock is carrying a quota number for 18 months straight. Base plus variable plus SPIFFs lands you 30 to 70 percent above a comparable L5 IC at the same company. No vesting cliff games. No promo committee politics. Most engineers at Salesforce or Stripe are optimizing for the RSU refresh cycle while the SE on their floor closes Q4 with a $40k SPIFF check. The number is the leverage. Carry it long enough to build pipeline instinct and you are now a technical closer with a W2 that embarrasses most Staff Engineers.

Meta fired 8,000 people and announced $145B in AI capex same quarter.

Microsoft's real AI moat isn't Azure. It's the capitalized software line burying a chunk of $27B in FY24 R&D. Capitalize more, expense less. Azure AI margins look cleaner than they are. Read the 10-K. Not the press release.

No one at your company runs a quarterly vendor RFP. That's why Salesforce, Workday, and your legacy cloud reseller print money off your renewal cycle every year. Ten percent reduction. Twenty if you have a real procurement person. At mid-enterprise spend that's $500k annually sitting in a line item nobody reviews. The tactic is simple. One day per quarter. Three vendors per category. Tell your current vendor the call is happening. Prices move before you send a single RFP. The bonus you're leaving on the table isn't a finance problem. It's a calendar problem.

Amazon $100B. Microsoft $80B. Google $75B. Meta $65B. Apple $30B.

Apple called ATT a privacy feature. It cost Meta and Snap north of $10B in annual ad revenue. Apple's own ad business grew the same year. Convenient.

Most engineers prevent outages and call it a good week. Nobody promotes you for that. The move is to convert your Sev-2 prevention into a P&L line. Mid-size SaaS bleeds roughly $12k per minute during an outage. A 30-minute avoidance is $360k in protected revenue. Write it that way in your promo doc. Not "improved system reliability." Not "reduced incident risk." Dollars. One number. One sentence. Staff Engineer packets that get approved read like business cases.

Anthropic at $900B requires 30x revenue growth in 24 months. The Pentagon already chose OpenAI, Google, and Nvidia over them. Someone is wrong.

Samir Q. was a sysadmin. He read the AWS commit tiers and found $1.8M in waste his director never saw. Negotiated a $12M multi-year deal. Bonus doubled. Vendor math is a Staff Engineer skill nobody teaches.

The fastest comp unlock in tech is not another RSU refresh. It is carrying a number. Sales engineer track. 18 months. Base plus variable plus SPIFFs lands 30 to 70 percent above equivalent Principal IC total comp at most enterprise software shops. Nobody in the Stanford CS pipeline talks about it because it sounds like you're admitting you couldn't make Staff. You couldn't. Neither could the SE making $340k at a Series B closing seven-figure deals. He just stopped caring about the org chart.

Longer context window is not a feature. It is a bill you pay before the request even finishes. The math is not subtle. Attention is quadratic. Double the tokens and you roughly quadruple the memory pressure and the compute cost. Most teams building on GPT-4o or Claude find this out around week three when their P90 latency starts looking like a bad SLA and their OpenAI invoice doubles for the same apparent workload. The product pitch and the infrastructure reality are not the same pitch. Anthropic ships 200k tokens. OpenAI ships 128k. Google ships a million on Gemini. Every one of those announcements reads as capability. Every one of them is actually a purchasing decision your infra lead has to live with. A 1M token context call at current inference pricing is not cheap. It is an experiment with a tab. And the tab compounds. Concurrent users. Retry logic. Evals that hit the full window. Suddenly your GPU allocation is not feeding a product. It is feeding a context buffer nobody asked whether you needed. The engineer question nobody asks in the product review is whether the user actually needs 200k tokens or whether the retrieval layer just was not good enough. Vector DB and chunked retrieval are not glamorous. They are also not quadratic. Selling context length is selling a number. Buying it without measuring P90 at load is just prepaying for a bad quarter.

CTOs quote GPU spend. They skip the power purchase agreements, cooling retrofits, and transformer lead times that add 30% on top. That number never makes the board deck. It surfaces in the emergency capex request six months later.

$300K liquid changes the recruiter conversation completely. Not because you'll say no. Because you can and they feel it. I've watched Staff Engineers at Google and Meta leave $50K on the table because they needed the offer. Needed it. That desperation leaks into every ask, every counter, every silence. Comp negotiation is not a script problem. It's a leverage problem. The engineer with six months of RSUs vested and parked wins the comp fight the other one never even starts. Build the number first. Then negotiate.

The "AI safety" debate is also a procurement fight. OpenAI, Anthropic, and Google DeepMind all have seats at the table when federal compute grant frameworks get written. That is not a coincidence. That is the point. The National AI Research Resource is a $2.6 billion allocation. The question of who sits on the oversight boards is the question of who controls which academic labs, which foundation model research, and which benchmarks get treated as the official standard of "safe." Whoever sets the safety benchmark sets the compliance cost. Whoever sets the compliance cost sets the floor that kills smaller competitors. This is regulatory moat construction dressed as ethics work. The staff engineers at these labs are not wrong when they say alignment matters. The problem is that "alignment" has a governance layer now, and that governance layer controls GPU allocation to external researchers. Grant committees are not neutral. They are staffed by people with vesting schedules. An Anthropic researcher on a federal AI safety board is not a public servant. They are a principal IC deciding which outside labs get H100 access and which ones run out of compute in year two of a four year research agenda. The safety debate is real. The capture underneath it is also real. You can hold both. The loudest voices on safety are also the ones writing the grant criteria that their competitors have to survive.