Wes Wagner ☕️

7K posts

Wes Wagner ☕️

Wes Wagner ☕️

@caffeinatedwes

I mostly ✍️ about technology, business, and ai. Occasional political RTs. VC-backed startup generalist ➡️ bootstrapped entrepreneur. 💼 @RarelyDecaf

Carmel, IN 가입일 Nisan 2011
2.5K 팔로잉2.9K 팔로워
Wes Wagner ☕️ 리트윗함
Harry Sisson
Harry Sisson@harryjsisson·
Trump is having a mental health episode right now. He’s been posting on social media all night. He posted at: 9:49pm (Ai Jesus photo) 9:50pm (Trump tower on moon) 10:10pm (dumb meme) 10:32pm (news clip) 10:53pm (news clip) 12:43am (announcing Hormuz blockade) 2:35am (article about Biden) 2:36am (article on naval blockade) 2:37am (article on Rep. Swalwell) 2:37am (posted the same article about Biden again) 2:38am (article on his ballroom) 4:10am (article on Iran) He’s not sleeping, he’s pretending to be Jesus, and he’s posting all night. He’s not well.
English
3.5K
14.7K
63.7K
3M
Wes Wagner ☕️
Wes Wagner ☕️@caffeinatedwes·
@RarelyDecaf Xano moving from "where you go to build" to "where you go to deploy" Lots of parallels to Vercel.
Wes Wagner ☕️ tweet mediaWes Wagner ☕️ tweet media
English
0
0
0
20
Wes Wagner ☕️
Wes Wagner ☕️@caffeinatedwes·
Xano's quiet bet on XanoScript is one of the most underrated moves in the backend developent space right now. It validates so much of what we're building at @RarelyDecaf. They're working on becoming THE compilation target for backend agentic development. (I imagine they'll probably change their @nocodebackend handle soon!)
English
1
0
0
81
Wes Wagner ☕️ 리트윗함
Jeff Wells
Jeff Wells@JeffWellsRigInt·
It's time for serious governments to say publicly what they must privately admit, that the President of the United States has lost his mind.
English
22
172
1.2K
11.1K
Wes Wagner ☕️ 리트윗함
Ilhan Omar
Ilhan Omar@IlhanMN·
This is not ok. Invoke the 25th amendment. Impeach. Remove. This unhinged lunatic must be removed from office.
Ilhan Omar tweet media
English
0
14.9K
100.7K
2.6M
Wes Wagner ☕️ 리트윗함
Paul Graham
Paul Graham@paulg·
@shaunmmaguire They're not against America. They're against Trump. Trump is harming American interests and, more dangerously, undermining the principles that make America great. By opposing him, they're supporting America.
English
132
119
4.1K
182.2K
Wes Wagner ☕️
Wes Wagner ☕️@caffeinatedwes·
I do this at a digital transformation agency. The wiki-like md output is something we call a "client graph", the structure of which comes from a template and methodology we created. Our business model is essentially a team of agents that build and maintain these client graphs. The value to clients is - bespoke, personalized ops and product strategy consulting - custom software Agents are the linters, and in reality, it's an entirely new programming language. x.com/caffeinatedwes…
Wes Wagner ☕️ tweet media
English
0
0
0
129
Andrej Karpathy
Andrej Karpathy@karpathy·
LLM Knowledge Bases Something I'm finding very useful recently: using LLMs to build personal knowledge bases for various topics of research interest. In this way, a large fraction of my recent token throughput is going less into manipulating code, and more into manipulating knowledge (stored as markdown and images). The latest LLMs are quite good at it. So: Data ingest: I index source documents (articles, papers, repos, datasets, images, etc.) into a raw/ directory, then I use an LLM to incrementally "compile" a wiki, which is just a collection of .md files in a directory structure. The wiki includes summaries of all the data in raw/, backlinks, and then it categorizes data into concepts, writes articles for them, and links them all. To convert web articles into .md files I like to use the Obsidian Web Clipper extension, and then I also use a hotkey to download all the related images to local so that my LLM can easily reference them. IDE: I use Obsidian as the IDE "frontend" where I can view the raw data, the the compiled wiki, and the derived visualizations. Important to note that the LLM writes and maintains all of the data of the wiki, I rarely touch it directly. I've played with a few Obsidian plugins to render and view data in other ways (e.g. Marp for slides). Q&A: Where things get interesting is that once your wiki is big enough (e.g. mine on some recent research is ~100 articles and ~400K words), you can ask your LLM agent all kinds of complex questions against the wiki, and it will go off, research the answers, etc. I thought I had to reach for fancy RAG, but the LLM has been pretty good about auto-maintaining index files and brief summaries of all the documents and it reads all the important related data fairly easily at this ~small scale. Output: Instead of getting answers in text/terminal, I like to have it render markdown files for me, or slide shows (Marp format), or matplotlib images, all of which I then view again in Obsidian. You can imagine many other visual output formats depending on the query. Often, I end up "filing" the outputs back into the wiki to enhance it for further queries. So my own explorations and queries always "add up" in the knowledge base. Linting: I've run some LLM "health checks" over the wiki to e.g. find inconsistent data, impute missing data (with web searchers), find interesting connections for new article candidates, etc., to incrementally clean up the wiki and enhance its overall data integrity. The LLMs are quite good at suggesting further questions to ask and look into. Extra tools: I find myself developing additional tools to process the data, e.g. I vibe coded a small and naive search engine over the wiki, which I both use directly (in a web ui), but more often I want to hand it off to an LLM via CLI as a tool for larger queries. Further explorations: As the repo grows, the natural desire is to also think about synthetic data generation + finetuning to have your LLM "know" the data in its weights instead of just context windows. TLDR: raw data from a given number of sources is collected, then compiled by an LLM into a .md wiki, then operated on by various CLIs by the LLM to do Q&A and to incrementally enhance the wiki, and all of it viewable in Obsidian. You rarely ever write or edit the wiki manually, it's the domain of the LLM. I think there is room here for an incredible new product instead of a hacky collection of scripts.
English
2.8K
6.7K
56.3K
20M
Wes Wagner ☕️
Wes Wagner ☕️@caffeinatedwes·
Focusing on memory as a generic concept hasn't provided too much value to me Intelligence does not come from perfect memory, but rather the thinking processes, mental models, and systems around that memory. My take: build your own memory systems to optimize on your goal.
signüll@signulll

no one has been able to solve ai memory yet. it’s brittle, it’s fragmented, & often times less helpful than not using memory. it’s an incredibly fascinating problem, way more of an art than a science at this point.

English
1
0
0
172
Wes Wagner ☕️ 리트윗함
MONETARY MAYHEM
MONETARY MAYHEM@MONETARY_MAYHEM·
Imagine thinking you were going to casually Maduro Iran but instead you collapse the global financial system and implode the petro dollar
English
114
3K
25K
318.8K
Wes Wagner ☕️ 리트윗함
Joe Kent
Joe Kent@joekent16jan19·
After much reflection, I have decided to resign from my position as Director of the National Counterterrorism Center, effective today. I cannot in good conscience support the ongoing war in Iran. Iran posed no imminent threat to our nation, and it is clear that we started this war due to pressure from Israel and its powerful American lobby. It has been an honor serving under @POTUS and @DNIGabbard and leading the professionals at NCTC. May God bless America.
Joe Kent tweet media
English
73.3K
217.1K
844.4K
102.7M
Wes Wagner ☕️
Wes Wagner ☕️@caffeinatedwes·
I think @steipete's architectural breakthroughs with @openclaw is making it obvious to many more people that AGI is here. What's missing is infrastructure: context, retrieval, loops, UX to proliferate through our day to day lives. That's solvable and will happen fast. The economy is about to get weird. Most people have no idea.
English
1
0
2
255
Wes Wagner ☕️
Wes Wagner ☕️@caffeinatedwes·
Building on this thought: the most consequential refactors for us are happening in markdown.
English
0
0
0
29
Wes Wagner ☕️
Wes Wagner ☕️@caffeinatedwes·
When I asked Claude, "what if I wanted to program in TS and JS?" Response- You mean writing both simultaneously? Like maintaining TypeScript source but also hand-editing the compiled JS output? That would be a nightmare. The abstraction exists precisely so you *don’t* think about the layer below. The moment you start caring about both, you’ve lost the benefit of the higher layer. **Where this actually happens** *Debugging*: You write TypeScript, but when something breaks in production, you’re often reading minified JS stack traces and source maps trying to correlate back. The abstraction leaks. *Performance optimization*: Sometimes you need to understand what JS the TS compiler emits. Certain TS patterns generate inefficient JS. You end up writing TS that’s shaped by knowledge of the output layer. *Interop boundaries*: Calling JS libraries from TS. You write type declarations (`.d.ts` files) that describe JS code in TS terms. You’re holding both mental models simultaneously. *Generated code inspection*: Looking at compiled output to understand why something behaves unexpectedly. “Oh, that’s how decorators actually work under the hood.” **The general principle** Leaky abstractions—Joel Spolsky’s term. All abstractions leak eventually. TCP pretends the network is reliable until it isn’t. SQL pretends you’re describing data relationships until you need to understand query plans. ORMs pretend you’re manipulating objects until N+1 queries destroy your performance. The skill isn’t avoiding the lower layer entirely—it’s knowing *when* you need to drop down. Most of the time you stay at TS level. Occasionally you peek beneath. But you don’t try to work at both levels simultaneously as a default mode. That cognitive overhead is exactly what the abstraction was designed to eliminate.
English
1
0
0
165
Wes Wagner ☕️
Wes Wagner ☕️@caffeinatedwes·
Natural language is now a programming language. But people don’t think about A) frameworks for it B) how the “compiler” (the model) works or C) which abstraction layer to stay in So they thrash—prompting, then hand-editing code, then prompting again. Like writing TypeScript and manually editing the JS output. AI coding isn’t going to be less efficient once the literacy catches up.
Mel Andrews@bayesianboy

A new study from Anthropic finds that gains in coding efficiency when relying on AI assistance did did not meet statistical significance; AI use noticeably degraded programmers’ understanding of what they were doing. Incredible.

English
1
0
0
419
Wes Wagner ☕️
Wes Wagner ☕️@caffeinatedwes·
@ray_deck Definitely 😎 I hadn't thought of looking at it as insurance. Along those lines, I imagine many firms will go the way of boiler explosion insurance—as the risk goes down, the services shift to inspection.
Wes Wagner ☕️ tweet media
English
1
0
1
19
Wes Wagner ☕️
Wes Wagner ☕️@caffeinatedwes·
This will happen across industries. Knowledge work's supply is increasing, cost is decreasing. But human accountability is finite.
SMB Attorney@SMB_Attorney

You guys don’t get it yet. Everyone keeps saying AI is going to replace lawyers. I don’t think people understand how this actually plays out. Let’s say you use AI to draft a contract. The contract misses something important. A year later it costs you two million dollars. What do you do? Right now, you sue your lawyer. In the AI world, you’d sue the AI company. Two things can happen. Option 1: The AI company has liability for legal advice. If that’s the case, every AI company will immediately stop letting consumers use AI for real legal work. The liability risk is massive. Option 2: The AI company has no liability because of disclaimers. If that happens, every state bar in the country will say consumers are being exposed to unregulated legal advice and call it the unauthorized practice of law. And they’ll shut it down that way. Either path leads to the same outcome. Consumer AI will be limited to generic “Wikipedia-style” legal information and LegalZoom level document prep. But the real AI tools? Those will live inside law firms. Lawyers will use them to move faster, analyze more data, and run way more matters at once. The M&A lawyer doing 5 deals at a time will do 50. Trial lawyers will run far more cases simultaneously. The idea that AI replaces lawyers probably dies. The more likely outcome is that AI supercharges the best lawyers and makes the profession even more profitable than ever.

English
1
0
1
159
Wes Wagner ☕️
Wes Wagner ☕️@caffeinatedwes·
@ray_deck For my business in particular, right now? Yes. Do I think that will change over time and that our offerings can be more self-service, also yes.
English
1
0
1
15
Wes Wagner ☕️ 리트윗함
Thomas Massie
Thomas Massie@RepThomasMassie·
The administration admits 🇮🇱 dragged us into the 🇮🇷 war that’s already cost too many American lives and billions of dollars. Before it’s over, the price of gas, groceries, and virtually everything else is going to go up. The only winners in 🇺🇸 are defense company shareholders.
Matt Walsh@MattWalshBlog

So he's flat out telling us that we're in a war with Iran because Israel forced our hand. This is basically the worst possible thing he could have said.

English
4.4K
19.4K
103.8K
2.9M
Wes Wagner ☕️
Wes Wagner ☕️@caffeinatedwes·
I currently expect "full time" team members to work 35 hours / week. I believe that hours ≠ output. With more powerful AI models and the infrastructure we build, the scarcity of our type of work moves towards judgement, taste, and human accountability. With that, l can see a future where it makes business sense to decrease the expectation to... 30 hours per week? 25? I don't know. But it's definitely not going to be the same.
Aakash Gupta@aakashgupta

The headline says AI intensifies work. What the study actually found is more interesting than that. Berkeley researchers tracked 200 employees for 8 months. AI made every single one of them more capable. They wrote code they couldn’t write before. They took on tasks they used to outsource. They moved faster on work that would have sat in a backlog for months. And then they burned out. Because the company changed nothing else. The org handed people a tool that 10x’d their ability to start new work, then kept the org chart, meeting cadence, review processes, and scope boundaries completely identical. Zero workflow redesign. This is like giving everyone a car and keeping the speed limit signs from the horse-and-buggy era. People drove faster because they could, crashed because nobody updated the roads. The self-reinforcing cycle the researchers found is worth sitting with: AI accelerated tasks → raised speed expectations → workers leaned harder on AI → scope expanded → wider scope created more work → more work demanded more AI. That loop has no natural stopping point. The company never installed one. Meanwhile, a separate NBER study across thousands of workplaces found productivity gains of just 3%. And an Upwork survey found 77% of employees say AI tools actually decreased their productivity. The pattern across all of this research is identical: individual capability goes up, organizational design stays frozen, and the gap between the two creates burnout. The study literally recommends companies build an “AI practice” with structured reflection intervals and scope limits. The researchers aren’t saying AI failed. They’re saying management failed to adapt to AI. Every CEO reading this headline as validation for slowing AI adoption is making exactly the wrong bet. The companies that win will be the ones that redesign the operating system around the intensity, not the ones that avoid it.

English
0
0
1
263