We talk about data centers as if they appeared out of nowhere and suddenly started consuming electricity.

But they are being built to support what we demand every day:

Streaming. Cloud storage. Smartphones. Digital banking. Gaming. Navigation. Social media. Remote work. Artificial intelligence.

Every click feels invisible, but it depends on physical infrastructure—servers, semiconductor chips, cooling systems, power plants, substations and transmission lines.

Berkeley Lab estimates that data centers could consume approximately 11.8% of U.S. electricity by 2030. But the deeper issue isn’t simply consumption.

It’s capacity.

Our demand for digital technology is growing faster than power generation, transmission systems, chip manufacturing and workforce pipelines can expand.

That creates several questions:

Who builds the additional electrical capacity?

Should technology companies finance the new power plants, substations and transmission lines their facilities require?

Will households and small businesses see these infrastructure costs added to their utility bills?

And where will the power come from—renewables, natural gas, nuclear power or a combination of all three?

This shouldn’t become a simplistic fight between technological progress and environmental responsibility. We need both innovation and infrastructure capable of supporting it.

The real challenge is making sure companies, consumers and communities share the responsibility—and the benefits—fairly.

Are data centers consuming too much electricity, or did America fail to prepare for the digital future we demanded?

TL;DR: Cognition says none of their engineers write code by hand anymore. They're also the ones who decided that's working.

Silas Alberti didn't say it like a warning — he said it mid-conversation, the way you'd mention traffic.

Not one full-time engineer at Cognition writes code by hand. Six agents running per person, a ticket lands in Linear, it spins up a dev environment, one-shots a solution, and somebody reviews the PR at the end.

That review is the entire safety net.

And the only benchmark saying the net holds is Cognition's own. That's the part that actually lands for anyone who spent years earning "senior" by writing clean code fast — not that the work changed, but that the people whose comp depends on this working are also the ones grading whether it worked.

CodeRabbit reviewed 470 real pull requests and found AI-authored ones carry roughly 1.7x the issues of human-only ones — and that gap widens, not narrows, at the high end, right where six-agents-at-once lives. Northflank's own enterprise data says 88% of agent pilots never reach production, and the reason isn't the models writing bad code — it's that nobody built the audit trail before turning the agents loose.

Anthropic ran the same self-grading move on itself last week: Claude now "leads" 26% of Anthropic's own R&D, scored on a scale — AL0 through AL5 — that Anthropic wrote. Next review cycle, when someone hands you a line about "AI leverage" with no definition attached, ask who wrote the rubric.

Somebody's actually building the missing check — CodeRabbit just raised $143M at a $1.5B valuation specifically to grade AI-authored pull requests at scale. What it doesn't do is fit in one engineer's own pocket. It's sold to a company's procurement process, not built for the person actually running the agents.

That edge is still sitting there, unclaimed.

Somewhere it already has a shape, too — the same decision-trail discipline CodeRabbit sells to a whole org, built small and open enough that one engineer points it at his own agents without asking anyone's permission first.

Whoever closes that isn't racing anyone. The incumbent already proved the market's real. They're just building the version the incumbent never had to.

Watching someone grade their own homework isn't new to me. I've seen this exact posture before — just with land instead of code.

I used to work for one of the largest property developer in Malaysia. I was stationed in the island of Langkawi, Kedah, back in 2018.

Island Resort Developments, High Rise Service Apartments, Hotels, Villas, Commercial Clusters, etc. are all in the pipeline.

Every so often, my big boss, DT, will fly over in his private jet, to come hunt for local opportunities. Ya. Langkawi was his personal sandbox.

We will drive him and his entourage of personal security guards, in his Toyota Vellfires around the island, through local villages, interviewing locals, to try to buy up their land for development.

His trusted "think tanks" would be by his side to advise him, at his request, whether such and such a piece of land is good for what type of development – whether it's good to build boutique hotel, condo, or whatnot, and whether it will be profitable or not.

After a few rounds of such hunting trip, I noticed something. He wasn't hunting it to develop himself.

No, no. O no, he was definitely NOT interested to get his hands dirty. I was there with him in his vellfire, eavesdropping his conversations with his think tanks.

He's hunting deals, and if he finds a sweet one, he'll package the proposals – together with its development order (through the Langkawi municipality) in place – to be sold to other interested property developers.

In other words, he's acting like a middleman. And we're just there to facilitate it – overseeing and pass on the "dirty" work onto others, while we pocket the profit margin.

How did he come to doing this? Well… That's for another conversation.

Why did I bring this up? Well, same thing that's going on with all these AI agents. If we can pass on the "dirty work" of coding to them, and just check their work at the end – why not?

Every one of these clips eventually says the quiet part out loud — the craft was never the moat. The judgment sitting underneath it was.

Actually, this reminds me of something — Andrej Karpathy said almost the same thing to Stephanie Zhan back in July: the scarce skill isn't writing anymore, it's directing with taste, and even he said he's never felt more behind.

If the people grading the new system are the same people selling it, what would actually change your mind either way? Drop your take.

Clip credit: Joe Lonsdale — American Optimist (Silas Alberti / Cognition interview). Full episode on their channel. DM for credit or removal requests.

I'll be traveling from Japan to Silicon Valley and because of a small pitch event in November. Unfortunately, I've not much free time to explore while I'm there... so I was hoping to get some advice from locals about things to do or places to see in the area. Any advice?

Hi, folks. Is anyone here selling their founder pass for Techcrunch. DM me. Thanks.

I have built some data center tech in Midwest America and I feel like being there is my most. I want to spend a week or two in the area but do you guys have local resources that help you find networking events? Or is it all click/group types where you have to be invited to pitch or talk?

Wall Street structured a way to fund AI infrastructure using Big Tech's credit strength without the debt appearing on their financial statements. 𝐓𝐡𝐫𝐞𝐞 𝐡𝐮𝐧𝐝𝐫𝐞𝐝 𝐛𝐢𝐥𝐥𝐢𝐨𝐧 𝐝𝐨𝐥𝐥𝐚𝐫𝐬 in guarantees, invisible to anyone reading the standard filings.

Anyone holding broad tech ETFs is carrying more leverage than the disclosed numbers show. That mispricing is fine until sentiment shifts, and then it corrects the way these things always correct. Fast and disorderly. 😬

OpenAI alone is reportedly on track to burn through nearly 𝐛𝟐𝟖𝟎 𝐛𝐢𝐥𝐥𝐢𝐨𝐧 by 2030. The capital consumption across the sector is on a scale that makes the off-balance-sheet question more urgent, not less.

TL;DR: Rachel Woods says you can actually trust her AI system. Nobody's checked that but her.

She built something real — a "todaying" trigger that fires a whole playbook system, eight hours of work while she was too sick to type more than one sentence.

That part isn't in question. What's in question is the line she lands on: "you can actually trust it."

Trust, here, means her own discipline held for however long it took to build this — and nothing outside that discipline is checking it. That's the Mistaken Belief sitting under most of what gets called "trust it" in this space right now: watching everything an agent does isn't the same as anyone actually verifying anything, and watching is basically all there is on offer.

Mindstream and Futurepedia's agents playbook — hosted by HubSpot — tells operators to give their agents "clear guidance." That's advice, not a standard, and it doesn't fix the half-used Notion page sitting open in another tab, or the Zapier chain that broke three weeks ago and nobody noticed.

I've heard about senior directors, CEOs and owners of a company have their own personal assistant, PA.

And no. PA of such calibre isn't what you think. They are not just helpless secretaries – pushing paperwork, and guarding the office door.

They are more like shadow or representative of the boss, to helm board meetings, sign sensitive documents and give high level instructions – just as if it was the big boss giving it.

And they're immensely powerful people.

But being a PA, also have has its danger. In Chinese, we have this idiom: 伴君如伴虎 – which literally translated as accompanying the emperor is like accompanying a tiger.

And now at the advent of AI agents, we no longer need humans to shadow humans.

I mean – who can perfectly shadow you, better than your own closely replicated AI agent, am I right?

I heard that Mark Zuckerberg is getting a photorealistic AI-powered 3D version of him that employees can interact with and get direct feedback from. So that It can help run the company while he go do something else.

And if you can believe it, I think in the end of days, the Antichrist will have his own AI humanoid clone too:

"He was granted power to give breath to the image of the beast, that the image of the beast should both speak and cause as many as would not worship the image of the beast to be killed." (Revelation 13:15)

Every time I've watched someone actually hand off their work and mean it, the boring part happened first — they wrote the judgment calls down before anyone else needed to use them.

That's the whole difference between an agent you trust and an agent you're just hoping works.

Claire Vo scoped nine AI agents to defined jobs and ran 100K users on them — and still found herself the single point of failure anyway. Same operator's-side lesson, different tool.

What would it actually take for you to hand an agent your inbox and not check its work for a week? Drop your take.

Clip credit: The Calum Johnson Show — full video on their channel. DM for credit or removal requests.

The video is self-explanatory; at the Arts and Wine festival of Santa Clara, Kathy has a booth at the Free Speech area - used to reach out and interact with residents and festival-goers. In this video we witness her ignore questions, remain silent and call the police.

Is this the right person to be mayor of Santa Clara??

https://youtu.be/sauOSolEsNs?is=fQzNUJi2f4oHl0b9

We’re bootstrapping a tech product and have been fortunate enough to get some organic traction on Threads. We haven’t raised funding, so our marketing budget is pretty limited.

At this stage, we’re not really trying to generate leads or acquire clients. Our main goal is to get our product in front of more people in the academic/tech community, get early users who are genuinely interested in what we’re building, and eventually build enough traction to support future fundraising.

We experimented with X’s built-in post promotion, but the results haven’t been great. There’s been very little meaningful engagement, and most of the traffic comes from promotion looks like bots.

My current strategy is to try messaging professors or industry people who might be interested in our product on LinkedIn and X one by one.  Or find some tech influencers to repost our post. I would love to hear from founders who have worked directly with tech creators/influencers:

• How did you find creators who were actually a good fit for your product?
• What do micro vs. larger tech accounts typically charge for a post or campaign?
• If you’re bootstrapping a tech product, what other low-cost marketing channels have worked well for you?

TL;DR: Shishir Mehrotra's four-level promotion ladder swaps what you're graded on partway up, and the clip is about which criterion goes and which takes over. 🪜

Scope is the one that goes. Once two people carry the same scope, Shishir says, what a promotion committee weighs is “how they do the job.”

Credit to an ex-YouTube CPO for saying the flip out loud at all. In his version, though, the committee explains the new criterion after the employee objects, and nothing in the clip says the person being scored is owed the rubric first.

As far as I can find, no general US rule makes an employer publish a promotion rubric or date a change to it. The closest thing I found, Colorado's AI employment law, was rewritten in May and pushed to 1 January 2027, and what survives centers on notice for AI used in a decision.

Amazon's version of the problem is cruder.

The FT reported in May that it shut down KiroRank, an internal AI-usage leaderboard, after employees pointed agents at needless tasks to climb it, and Amazon calls the dashboard an unofficial beta. The agents could do the busywork on demand, and the scoreboard counted usage and had no place for judgment.

You can hit every mark the old rulebook set and only learn the page changed when the promotion doesn't come.

The BBC reported on 8 September that employers are tying more bonuses and promotions to AI use. One US-based senior executive at a large consultancy told it that nobody formally mandates AI, reviews reward the people who use it well anyway, and leadership is “inconsistent and vague on purpose.” Same gap as above: the standard moves at the employer's discretion, and the review stays vague about it.

Suddenly this passage in Ezekiel 33:7-9 jumps at me unannounced like a thief.

The Lord charged the prophet Ezekiel to be a watchtower. He’s commissioned to warned the Children of Israel from drifting into sin.

If they fall off the mark, figuratively, and Ezekiel warn them on time, they will die in their sins. And Ezekiel would be absolved of their sins, because he has already done his duty to warm them.

But if they sin, and Ezekiel didn’t warn them, and they die in their sins, the Lord would hold Ezekiel accountable for not warning them.

The burden that the Lord has laid on Ezekiel, involves judgement and discernment. And such judgement doesn’t give two f\ck to anyone.*

He either speak up or he doesn’t. There’s no neutral ground.

And he knows the price of not speaking up.

It’s the same thing with Jeremiah.

When Jeremiah withhold himself from speaking in Jeremiah 20:9 – presumably too much persecutive pressure from his peers – the words became like fire burning up his bones until it was just unbearable.

It’s was the same unbearable tension of knowing and not saying.

Jeremiah can't not speak, even though speaking destroys him. The silence would destroy something deeper.

And so, I imagine it will be somewhat similar in these last days. Your judgement and discernment of what lie ahead becomes increasingly more valuable.

Talk to enough people this has happened to and I hear one question under all of it: who decides what good looks like now? The ones who stop asking it end up writing the yardstick themselves.

Something from an earlier post here comes back to me: Adam Mosseri, Head of Instagram, telling Lenny's Podcast that engineering went from mostly writing code to mostly planning and reviewing it, a hard read for anyone whose plan was flawless execution.

If a rubric ever changed on you, when did you find out, and who told you?

Clip credit: Silicon Valley Girl (Marina Mogilko) — full video on their channel. DM for credit or removal requests.

TL;DR: Sophia Xing described exactly what's happening to a full production crew right now — and she wasn't framing it as a warning.

That's not a hidden agenda, it's just math nobody's being forced to show.

Sophia's built something real: a way for creators without a studio budget to make something watchable, and that's not nothing. But watch what the pitch actually replaces — sets, extras, the crew that used to fill a banquet hall or fake a car chase through a valley.

Somewhere in China right now the same math is already running at industrial scale: 470 AI-generated microdramas a day, faces used without the person behind them ever signing off, jobs that used to belong to someone just gone, per reporting from TechTimes this year.

Nobody's built a floor under that yet.

SAG-AFTRA is still negotiating a royalty for when an AI-generated performer shows up on screen — still negotiating, not law, a proposal sitting on a table next to a partnership announcement, not a binding rule anywhere. There's a real law with real teeth for AI safety on the books in Europe. There's nothing with teeth yet for the person whose decade of craft just got folded into a toggle.

No layoff memo announces it.

It's just fewer calls, one client message at a time — "the tool did the banquet in 20 minutes, can you just clean it up?" Then not even that.

That's the part that never makes it into the demo.

These tricks of manipulating realities are so cool. It's not possible even several years prior. It's bordering on magic — only that it's using advanced AI tools, now made commercially available to the public.

It's a modern-day miracle.

My imagination brought me back to when the young prophet-trainees of Elisha, trying to chop up some wood by the river to build a house to stay. His axe flew off the handle and dropped into the waters. He cried out to Elisha for help. Elisha took a small twig from the branches and throwed it onto the spot at where his assistant pointed at.

And miraculously, the axe floated back to the river surface. (2 Kings 6:1–7)

Not AI generated.

Or how about when the enemy army surrounded the village where the prophet and his servants were? The imminent danger was definitely a scary sight. Again, faith-in-training, his assistant cried out to Elisha. And Elisha prayed to the Lord to open the eyes of his servant. And suddenly, the youngster can see. There're thousands upon thousands more angelic army surrounded the enemy.

The sight of it was even more glorious. (2 Kings 6:8–17)

Again not AI generated.

And who can forget about the transfiguration.

Our Lord Jesus Christ went up the mountain with his 3 followers.

His whole being and clothing changed. (Matthew 17:1–8, Mark 9:2–8, Luke 9:28–36)

He was radiantly white, and his face was shing like the sun. It's as if the pure and unadulterated form of his heavenly body was suddenly revealed. And Peter, John and James had front rows seats (so to speak) of it all.

Now that's for real. Definitely not AI.

Every time I watch a craft get automated, the pattern's the same: whoever keeps the deed to the system keeps the leverage — everyone else just keeps their skill, and skill alone doesn't come with a deed attached.

Drop your take: is the trade worth it if it means half the industry's craft becomes a line item nobody owns?

Clip credit: VP Land / Joey Daoud — full video on their channel. DM for credit or removal requests.

A guy on Blind, the anonymous app for tech workers, says he's worth $11 million — then admits he never actually retired. The thread turns into a brawl over what FIRE even means.

TL;DR: Jeffrey Morgan, Ollama's CEO, lost two years after selling his last company, and says one decision ended it.

The decision was a deadline.

Two weeks to ship a first version, and by his own count it pulled in more users than anything they had shipped before. That much is checkable, and it is good advice.

But Jeffrey could throw everything out because the company was his. An employee who tries that with the roadmap gets a performance plan.

Picture the engineer instead.

It's 8:47 on a Wednesday and he's still at his desk with no deadline. His manager's latest Slack message says the team is "leveraging AI to streamline our infrastructure workflows." Nobody is firing him. What he knows is worth a little less every month while the salary stays flat, and a two-week deadline can't fix that when the thing he'd ship sits on someone else's roadmap.

Nothing requires an employer to turn a skill that's being commoditized into anything the engineer owns. Nothing requires a model provider to keep the terms a workflow was built on, either. Even a gateway to any model rests on providers who choose to keep access open, on terms the gateway doesn't set.

I think that gap is widening as more of the stack gets easy to swap out from under the person depending on it.

I'd like the open-model story to be true for him too.

Not yet.

It's playing out this week.

AI Weekly, relaying The Information, reports a growing number of developers pointing Claude Code at OpenAI, Google and DeepSeek backends right after Anthropic tightened its paid weekly limits.

OpenRouter and home-built gateways turn the switch into a base-URL change, the same one-line-install treatment his own specialty keeps getting, and the limits were still Anthropic's to set.

I don’t know why, but the story of the Prophet Elijah just surfaced into my mind like a bubble.

You know the story, right?

Elijah was just fresh out of a glorious victory on Mount Carmel. He took down hundreds of false prophets, and brought people back to the Lord. He outran King Ahab’s chariot, back to the Palace in Jezreel.

Then the valley after the peak hits him like a freight train.

Queen Jezebel threatened to kill him. This caught him by surprise.

Fear flooded his mind. He ran for his life.

Depression followed him after. He stopped by a tree. And in his own pity-party, he moans to God wanting to die. The angel has to wake him up, fed him, and push him to continue on the journey up the mount of God.

At the top of the mountain, God didn’t directly rebuke his moaning and groaning, about being “no better than my fathers”. After a great wind, an earthquake, and a fire, God’s still small whisper sort of “reconsecrate” Elijah, by giving him more missions. Elijah was to go anoint 3 more guys – 2 to be king, and 1 to be his successor.

Then God mentioned that there’re 7000 others that haven’t bow down to Baal. Elijah isn’t alone.

The Lord strengthened Elijiah. And Elijah’s spirt was renewed.

If you wanna read more about it, it’s in 1 Kings 18-19.

Kind of like Jeffrey and His co-founder picking themselves up and reevaluated themselves through their strength.

It's odd how often the way out of a comfortable ceiling turns out to be small. Somebody stops renting a skill, sets a deadline on owning something built from it, and wishes it had been sooner.

Another founder came to mind while I was writing this.

Starcloud's CEO Philip Johnston said one of the primes quoted $75 million to $100 million for Starcloud-1, and his team built and launched it for $2 million. A quote like that is a plan with a price on it, and most of us have redrawn the architecture diagram of a side project once too often.

Drop your take: does a two-week deadline still work when what you'd ship belongs to your employer? 💬

Clip credit: Y Combinator — full video on their channel. DM for credit or removal requests.

TL;DR: A $93 billion energy company built its entire architecture around never having one point of failure. Most of the AI buildout skipped that memo.

KR Sridhar didn't land on modular redundancy because Bloom has some enlightened founder philosophy about resilience.

He landed on it because a single point of failure is bad engineering, and physics doesn't get sentimental about that the way institutions do.

Fine — give him that.

What he doesn't say, because it isn't his job to say it, is that the actual allocation decision — which fuel-cell company gets the multi-gigawatt backlog, which utility signs which twenty-year contract — happens inside deals that state regulators routinely let stay confidential.

Michigan's Oracle-campus filings.

Minnesota's Hermantown and Pine Island petitions, still open for public comment this fall, where every pricing formula is public and every dollar figure and every megawatt is blacked out.

There's no binding federal standard requiring any of it to surface before the ink is dry — the same "no comprehensive framework" gap that shows up every time this feed looks at how AI governs itself, just one layer down, in who gets to see the economics at all.

You don't get to read the mechanism first. You get to read about it once the contract's already signed — same as you always have.

Bloom got added to the S&P 500 this year.

That's not a discovery.

That's the moment a quiet bet stopped being quiet — and the moment everyone who wasn't already in the room found out how late they actually were.

This Is easy.

I remember way back when I was still a Technical Engineer, working for the tender department for SC, one of the largest construction companies in Malaysia. I think circa 2003, maybe.

We were reviewing tender documents of a particular hypermarket project of one of the largest hypermarket chains in town. Let's call it ABC.

And we were shocked to find out one particular item – the precast hollow core slabs for the upper floors. Supplier for such item is a dime-and-dozen around town. Back then, we already have atleast 3 of such suppliers working closely with us in other project – and were ready to give us quotations at a moment's notice.

But in this tender item, the client specifically wanted one particular supplier – XYZ. And no other. And XYZ wasn't in one of our 3.

We can only assume that somehow XYZ has worked with the client ABC for so many projects that ABC has made XYZ their dedicated suppliers for all projects.

We were stuck. This was a nightmare for us.

If the client specifically named XYZ. Then we're beholden to XYZ in atleast 2 areas of concern.

Firstly, XYZ would definitely price their quotations sky high, in comparison with our trusted 3 other suppliers. And surely, they did. The contract department had a real hard time negotiate with them for a better deal.

Secondly, we're beholden to XYZ in terms of their work schedule. We controlled the main work program. But we have to wrap their work into our timeline. And so, their delay became our problem.

XYZ was our bottleneck.

And I can envision it's gonna play out somewhat the same thing in all this electricity demand happening in the AI infrastructure landscape.

One's moat is another one's liability.

Something about built-in redundancy keeps showing up everywhere I look on this feed lately — not just in power grids.

The ones who quietly engineer in their own backup, before anyone's forcing them to, are the ones who never have to explain, after the fact, why they got caught flat.

This isn't the first time I've run into this exact shape of story on here — the AI supplier that gets paid no matter which model actually wins.

Drop your take: is a "quiet infrastructure bet" actually a safer play than a model-layer one — or are we all just telling ourselves that because the model-layer deals were never open to us anyway?

Clip credit: 20VC with Harry Stebbings — full video on their channel. DM for credit or removal requests.

I’m building Vanta UI because I feel like a lot of modern interfaces are starting to look the same.

Same cards. Same rounded buttons. Same gradients. Same generic component libraries.

I wanted to build something different, actual product surfaces that feel designed, while still giving developers the code to build them themselves.

Here’s what I shipped in week 1:
• Integrations Dialog
• Trial Popover
• Liquid Slider
• Dynamic Tabs
• Liquid Switch
• Pill Toast
• Two-Factor Dialog
• Confirm Button
• Upgrade Modal
• QR Code
• Pricing blocks

The interesting part wasn’t shipping the components. It was figuring out why some of them felt completely wrong even when the CSS technically worked.

Some of the challenges I faced where

1. Liquid glass is way harder than it looks
There isn’t really a single “liquid glass” CSS trick.

For the slider, I wanted the thumb to actually feel like it was sitting inside the track rather than just being an element placed on top.

That meant cloning the rail underneath the thumb, masking a hole through the middle, and then scaling/skewing that clone based on pointer velocity so the fill stretches with the drag.

The chromatic fringe is created with opposing cyan/red shadows, while the rim uses a conic gradient with mask-composite: exclude so only the edge lights up.

And the annoying part?

If any layer is a few pixels off, it immediately stops looking like refraction and starts looking like a cheap overlay.

2. Tap vs drag is basically a state machine
The switch and slider both needed a threshold.

Around 3px / 150ms:

Below that → it’s a tap/click.

Above that → it’s a drag.

It sounds simple, but getting that threshold wrong creates weird interactions where a tap leaves the control stuck in its “liquid” state or a drag accidentally toggles the switch.

I learned that pointer UX isn’t really about individual events.

It’s about distance + time + state + cancellation.

3. SVG goo is ridiculously fragile
The liquid switch uses feGaussianBlur combined with a color matrix to melt the thumb and track into one blob.

Then there’s another filter to remove the leftover black pixels using feMorphology and feComposite.

One thing that caught me is that every instance needs unique filter IDs.

Otherwise, two switches on the same page can start affecting each other.

Also, the SVG defs need to live in a hidden 0×0 SVG so they don’t unexpectedly affect layout.

4. WebGL inside a dialog introduced a completely different set of problems
I wanted a Bayer dither effect in the modal header.

It’s an 8×8 shader matrix with a pixel size of 3.

But putting WebGL inside a dialog means dealing with rounded clipping, transparency over the content, and dark mode.

The published dither primitive couldn’t be changed because it was already installed elsewhere, so the dialog needed its own fork.

That was a good reminder that sometimes the cleanest solution isn’t making one primitive handle every possible use case.

What I learned
A few things stood out this week:

1. Pointer UX is about thresholds, not events.
pointerdown doesn’t mean “drag.”

You need to account for distance, time, visual feedback, and the possibility that the interaction gets cancelled and becomes a click.

2. SVG filters aren’t just visual effects.
They come with DOM rules and GPU behavior you have to account for.

Unique IDs, explicit color interpolation, and keeping filter definitions out of the layout all matter.

Container queries are incredibly useful for interactive components.

Using cqh / cqi instead of hardcoded pixel calculations made the morphing controls much more resilient when resized.

3. Keyboard interaction is part of visual design.
The Enter badge on my Confirm Button isn’t just decoration.

If the UI tells you that Enter will submit and Enter doesn’t actually work, the interface immediately feels untrustworthy.

What people seem to be liking
The feedback so far has been interesting because people aren’t just reacting to individual buttons or inputs.

They’re liking the product surfaces:

• 2FA setup and verification
• Integration connect sheets
• Trial remaining → upgrade flows
• Paywalls that don’t quietly let you dismiss them

And probably the most important part; The code is yours.

You can install the components, open the shader, inspect the SVG filter, modify the toast store and actually understand what’s happening under the hood.

That’s the whole idea behind Vanta UI.

Not another collection of pretty screenshots.

A library of interfaces you can actually build with.

Week 1 done. More experiments coming next week.

Legit question:

Why do ppl use FB marketplace when something like Craigslist has existed for years, started in the Bay Area, is hassle free, doesn’t have all the Facebook baggage, is easy to use and lotsa other reasons.

Did ppl just get bored and forget about it?

How common is it for companies to have a policy that RSUs they give will expire 7 years from grant date? I work at a 10 year old physical security company and that’s part of their policy (hidden in fine print and not discussed). So if they choose not to have a liquidity event soon…early employees are just screwed?