David Demaree (@ddemaree) header
David Demaree (@ddemaree) profile picture

designer, writer, product person, agent wrangler • founder @bitsandletters • Formerly @adobe, @google, @stripe, @webflow

beyond the swamps of jersey
Joined November 2006
Photo by David Demaree (@ddemaree)Photo by David Demaree (@ddemaree)Photo by David Demaree (@ddemaree)Photo by David Demaree (@ddemaree)Photo by David Demaree (@ddemaree)Photo by David Demaree (@ddemaree)Photo by David Demaree (@ddemaree)Photo by David Demaree (@ddemaree)Photo by David Demaree (@ddemaree)Photo by David Demaree (@ddemaree)
ChatGPT Codex is the new VS Code
1
2
1
6
1,116
David Demaree retweeted
I just finished talks about my software factories at two conferences. Afterwards a bunch of people came up and told me what they were surprised about. Here is a distillation of what people thought were hot takes from my two talks. First hot take: I tell everyone to slow down. Most speakers go on about how fast they're going, but I strongly believe in pacing AI outputs to human speeds. I regularly tell AI-pilled CIOs and CTOs to chill: almost nobody is _actually_ going fast with AI. Engineering still moves at engineering speeds, and business moves even slower. The ones pushing too hard are starting to see downtime for it. If you don't pace your AI to human speeds, everything starts breaking around you, even at small operations like my online video game. I only have about a dozen humans working with my factory, and only a few hundred active old-timer players in the community who get along well, and still, introducing AI has still been very rocky. My agents have, at times, overwhelmed my players with features, my accountant with emails, my merge queue with tickets, and my machines with load. Agents have pissed off my admins, resulting in name-calling, they've made messes in the game, and they've launched broken OSS without permission. The list goes on. I can get away with all this chaos because everyone involved in my operation is very forgiving. They're excited by the potential. But even so, I had to learn to slow down, real fast. And so that's what I preach. Hot take #2: Should you buy a software factory? Do you even need one? No. You probably don't need one. Factories take an extraordinary amount of upkeep. They turn into garbage mountains unless you put a frightening amount of time and tokens into curating them. I had to burn my previous five factories down since it eventually became cheaper to rewrite them than to fix them. So I'm not out there advocating for software factories or swarms just yet. If you do want one, be aware that it is a significant commitment of both money and human leadership to keep one running. Several people told me that I was the only one who stood up onstage, at either conference, and said Build, don't Buy. But my experience is that software factories grow to be highly bespoke to your domain. Mine is super tangled up with my game, and I think that's inevitable. Because the factory is not just building my product, it's supporting it too. It's a company in a box. And they're easy for Claude to build for you. Third and arguably hottest take: Next year will have a lot of human/agent and agent/agent office drama, resulting from bringing in AI employees, and it will be gloriously funny, but also frustrating. Many of you are already on this bandwagon, but everyone next year will have a personal chief-of-staff agent. Busy people, even hobbyists, will have whole entourages of helper agents. The hot take is that people will become so dependent on these little private entourages, that they'll bring them to work. Your people will talk to my people, etc. Whole protocols will emerge for private entourages negotiating work between humans, inside companies big and small. Nearly all humans will wind up having to start working with AI employees next year, and it'll be the beginning of the biggest cultural change we've seen in a hundred years. So that's the hot takes. Slow down. Only build a factory if you think you really need one. And focus on empowering yourself with your own agentic chief of staff (or team). Your entourage will define how you work with others, so start by perfecting how you work with them yourself.
191
316
106
2,914
339,332
David Demaree retweeted
Today, the promises of transhumanism and posthumanism are multiplying. These are ideological currents according to which, sooner or later, technology will eliminate all disease and pain, as well as aging and even death itself. Precisely because scientific progress is a supreme achievement of human intelligence, it must not be confused with a privilege reserved for millionaires seeking immortality, while entire peoples suffer from poverty and oppression. In the face of this mirage, which promotes the illusion of human beings perfected by cybernetics and biotechnology, Christian anthropology reminds us that a limitation is not a manufacturing defect, but rather the very condition of human grandeur. #ApostolicJourney #Peru #MagnificaHumanitas vatican.va/content/leo-xiv/e…
1,713
8,847
1,958
69,054
4,837,580
David Demaree retweeted
'Monosyllabic' is not. ‘Abbreviation’ is 12 letters. ‘Thesaurus’ doesn’t have a synonym. 'Non-hyphenated' is hyphenated. Say what you will about English, but it has a sense of humor.
118
1,285
54
11,272
172,739
David Demaree retweeted
some people are just stuck in the past
33
37
11
753
54,282
There is no substitute for the person who Knows What To Do.
1,318
4,862
482
41,422
2,999,606
If a CEO hypothetically wanted to make his departure maximally painful for the company he would have: No successor, no COO, no president besides himself, dozens of direct reports, no 1:1 coaching for any of them, a cult of personality, and all key company contacts as his personal relationships This is going to be tough
71
120
40
4,271
591,604
David Demaree retweeted
"Anything the model can do is broadly distributed, so everyone has access to it, which means it's not that valuable. The valuable thing is how a human uses that." — Dan Shipper (@danshipper), Every at @every Thesis 2027
3
16
2,149
David Demaree retweeted
Hear me out: We hated "waterfall" because after Big Upfront Planning, implementation took FOREVER, and by the time we were done, the plan was out of date But with AI, implementation is rapid (100x faster, or more, than before) So Big Upfront Planning can now make sense?
586
88
83
2,372
175,039
David Demaree retweeted
the problem with writing an essay is you really think you know what you're going to say and then you say it and it's ordered wrong and then it's too long and then it doesn't hang together and then it doesn't have its meat anymore and then... sadly, AI cannot yet help with that
66
18
12
487
48,714
David Demaree retweeted
One of my favorite research practices I learned at @inkandswitch is “preinfusion”. The term comes from espresso (I believe @pvh coined it?) - and the original meaning is that you have a lower pressure soak before you turn on the high pressure and pull the shot. The way it works at the lab is that you patiently let a cluster of ideas slowly form and develop, meandering somewhat in the background, and you lay the groundwork to work on them more seriously… before starting an intense high-pressure sprint. Could be a few months of part-time preinfusion before a hardcore 3 month project. This really helps avoid the problem where you’re trying to sprint, but you don’t actually have enough clarity to know where to run. I think this applies in many other contexts. Preinfuse before trying to write an essay. Preinfuse before raising money for a company. A slow and patient preparation can enable swift follow through.
40
34
11
617
29,869
David Demaree retweeted
I know it hurts to hear but you are trying to be too smart with ai I’ve found I get better results the dumber I am it’s weird but it’s true
58
10
13
369
36,834
David Demaree retweeted
I'm not sure that people want to live this way. Well, I think 10% of people want about 20% of this. And 0.001% want 100% of it. Having spent 2005- 2020 trying to make up good use cases for tech, it dawned on me this isn't how people are. Nor is the world built for this.
187
70
39
1,198
138,462
David Demaree retweeted
at least the cybertruck gave us this quote from a 2025 WIRED profile of various owners wired.com/story/owning-a-cyb…
38
1,824
16
21,592
361,355
David Demaree retweeted
The future of work is that we'll all work in niche and mysterious religious sects.
Church for a niche and mysterious religious sect, or AI conference on the future of work? Trick question, it's both.
3
4
9
2,664
David Demaree retweeted
we can't do "it's not my job to educate you" this go around, woke 3.0 we are all volunteer teachers
I walked the Trump rally line to listen, not make assumptions. I talked with voters, asked questions and heard what matters to them. When I'm elected, I'll represent all 82 counties and every Mississippian, no matter who they voted for. That's what being your senator means. #MississippiMatters
61
2,607
50
32,730
443,574
David Demaree retweeted
WHY ARE THERE SO MANY CVES (we know why)
20
20
2
377
28,620
David Demaree retweeted
AAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
Today we're sharing with you all the name of the next Elder Scrolls title (did you guess correctly?).
3
84
1,582
David Demaree retweeted
A design school case study could be written about the series of events that led to this Transactions view, on a full desktop browser, showing precisely zero transactions.
this company is worth 70 billion dollars
24
20
3
497
32,912
the cargo culting of MTS has been hilarious to see. a set of highly competitive companies whose employees are at constant risk of poaching decided to give everyone a flat external-facing title to obscure their specific organizational role. internally, those roles exist and are explicit, because of course they are. a bunch of upstarts then saw the external-facing titles and thought it was what the labs do internally and copied it for clout and because ‘it’s what the big labs do’ without understanding the context or purpose. they then ended up with unclear org structures because they copied a redaction thinking it was the actual structure.
MTS-ification is flattening most categories of tech work It's probably the most interesting and import idea to absorb and study to understand the future dynamics of the job market, and how to take advantage of them TLDR is that titles used to describe "what we do", post-AI they describe "what we own". Depth is rentable, so passing work around costs more than doing the work itself. AI can fill in the "average" so what’s left to stand out is a combination of agency, judgement, and spike: the thing(s) you do better than almost anyone. Invest in and become fluent with as many relevant AI tools (and techniques) as possible, be able to explain simply and clearly how you can use them to expand your capacity and span adjacent specialties complementing your main. Emerging categories to position for (beyond MTS): Growth staff (me): marketing / sales / partnerships / community / devrel Operations staff: finance / people / legal ops / internal tools Customer staff: support, customer success, account management, solutions engineering, implementation In interviews and on resumes 1. Lead with your "spike", have ultra-crisp stories where it was the reason behind a great success 2. Have ultra-crisp stories exemplifying agency and good judgement that have driven some outcome end to end and the impact 3. Say “I,” not “we,” and be ready to describe exact details There are big changes and things are being shaken up, with all disruption though there are always tons of opportunities, the people who move quickly and get in front of them the fastest will have the most upside. There are SO many new companies with crazy growth, pre-unicorns and new unicorns hiring like crazy, you want to be part of a company that will 10x or 100x over the next 10 years, not one that is about to have to reshape everything because they themselves are being disrupted.
5
8
1
309
24,123