
Communications @awscloud. I enjoy exploring, fitness, nutrition, baseball, and playing guitar.
Chicago, Illinois
Joined August 2008
- Tweets17.4K
- Following1.1K
- Followers1.6K
- Likes14.2K
Hetfield’s statements over time have focused on creating a place for the Metallica family to come together for the music and the community. He just doesn’t want to create walls between us. Every Metallica fan I know is so thankful for what they’ve brought us.
The Metallica frontman seemingly took a pot shot at artists who use their platforms for political means during a brief speech on stage in Las Vegas loudersound.com/bands-artist…
1
130
Zach Solomon retweeted
I just read what Zuck wrote about Muse connectors.
A few things I think this means:
1. We’re witnessing the agentification of consumer apps.
2. Zuck believes Muse reaching 100M+ users feels entirely possible.
3. Whoever you connect to becomes your new landlord, so pick carefully.
4. Connectors become the new app listings (valuable real estate).
5. Being early could be as valuable as being early to the App Store in 2009.
6. Meta sees what people want, which providers convert, and what users will pay. That gives it the power to rank connectors, charge for distribution, and launch competing services.
7. The opportunity map includes agent native APIs, connector agencies, SEO for agents, identity and reliability infrastructure, and vertical connector marketplaces.
8. We’re moving from humans choosing apps to agents choosing businesses.
9. Every business will need an agent strategy, just like every business needed a mobile strategy.
10. Kinda crazy to say but a 3 person API company could reach 10M+ users through one great connector.
11. Connectors could create an entirely new second-order economy. The biggest opportunity may be helping businesses distribute, price, and optimize their services for agents.
12. Your API becomes more important than your app. Weird to think about but true.
13. Zuck wants Muse to own the moment between wanting something and getting it. He is coming for the app economy. Will he win? Right now it's Instinct vs Muse vs Grokbot. TBD.
Opening access for developers to build Muse connectors. You bring the API -- Muse brings the agent, the browser, and the context of what the person actually wants. People reach your service just by asking for it, and their agent takes it from there.
New connectors are live today. Come build with us. muse.ai/platform
This feels significant. I was added to a @muse beta with voice calling. It called contractors just now, sent an email with photos to follow up, and I don’t even need to be present for the estimate.
Those who get good at agent to agent are going to absolutely clean up.
I can’t remember the last meeting I had when I wasn’t running Kiro or Claude Code in the background. It’s absolutely becoming clear how AI is doing as I’m steering and aligning.
95
I've been doing exactly this for comms strategy work — a structured markdown workspace with 100+ curated documents, voice profiles, context layers, and templates that the AI operates as a teammate. Organizing the knowledge and context is the differentiator.
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.
131
when starting my career in comms, it was almost frowned upon to be technical — they positioned you as an individual contributor doer, not a strategic high potential employee. Unreal how wrong they were, and that never sat with me well. AI has allowed me to merge both.
generalists are about to win big
If you understand a little of tech, business, and people, and can connect everything fast.
you're sitting on a goldmine right now.
84
I honestly can’t think of many companies with a more consistent global experience as @uber.
Used it in three countries this month and it’s reliable, same look and feel, safe drivers, etc.
46
An important part of human + AI is understanding the situation. Use AI to figure all this out, but you from a position of observations and offering help, vs being the expert at their job. Humans still lead with empathy.
someone used claude to get a traffic light reprogrammed in his town
and the state engineer responded within a week and reprogrammed the light the next day
claude makes you sound like an expert so that you don't get ignored
71
It’s kind of wild to think that you can build a basic app with basically as much effort as signing up for an Apple developer account.
68
this is the part that jack wrote
you can tell because it's got the curly quote and the rest has straight ones
the whole post is well done, he has a comms person who is a highly skilled prompter
but jack added this part before hitting post
and i like that about jack
we're making @blocks smaller today. here's my note to the company.
####
today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone.
first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay.
we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly.
i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures.
a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers.
we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold.
to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward.
to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow.
jack
Right now, one of the most important things you can do if you want to get good at AI is to organize your data.
This also I feels like folder/file naming conventions 2.0 — organizing conversations makes you more effective and it’s easier to track things down.
44
Most workplace frustration isn't about bad strategy. It's about waiting on people who said "I'll get to it."
A thread on how to actually get busy people to follow through 🧵...
1
58
Close the loop. Show them how their input is welcomed and the value they brought. How did they contribute to the outcome? This is your chance to actually build a relationship vs a transactional colleague.
1
35











