AJ Morris

This is where enterprise organizations will fail. There is too much structure, policy, hoops to jump through. Give them constraints without the hassle and see what they can create!

no 👏 more 👏 permission prompts 👏

5% of employees are doing sophisticated work with AI—treating as a reasoning partner, delegating complex tasks, ambitious usage—and the best users are above manager level! Interesting data: hbr.org/2026/03/what-t…

Another feature that goes directly after openclaw. Between this and dispatch, I might not have a need for openclaw much longer. 😉

2 minutes. That's how long it took to have code written. I spent 15 minutes describing a bug and putting in constraints for how we could address it. I spent another 15 describing the goal. Planned and Executed. 💥

@Codie_Sanchez @m_franceschetti I don’t enjoy social media but build 1-2 apps per week. Let’s chat.

@m_franceschetti Exactly. I need more of them.

Best money I've ever spent as a CEO... an internal AI transformation hire. He doesn't care about title. He just wants to ship. And he goes across your entire org, sales, revenue, hr, apps, tech and kills stupid manual processes. Such an underrated unlock I have since hired 2 more.

This is an interesting concept. Something I’ve been playing around with that’s a little different though is @Tailscale and a private network. I can access a number of my apps from my devices anywhere.

My current system prompt for Codex / Claude Code I aim to improve: - Collaboration - Critical thinking - Autonomy - Remove guesswork - Clearer writing - ADHD friendly Full prompt in thread

Boris Cherny (Head of Claude Code, Anthropic) just dropped ~90 mins on Lenny's Podcast about what happens after coding is solved. Just the clearest thinking I've heard on where software is actually going. My notes: 𝟭. 𝗖𝗼𝗱𝗶𝗻𝗴 𝗶𝘀 𝗹𝗮𝗿𝗴𝗲𝗹𝘆 𝘀𝗼𝗹𝘃𝗲𝗱. Boris has not edited a single line of code by hand since November 2025. He ships 10 to 30 pull requests every single day, all written by Claude Code. He is one of the most prolific engineers at Anthropic, just as he was at Instagram, except now he never touches a keyboard for code. I built an entire iOS app, @10minutegita, without writing a single line of code myself. No CS degree, no bootcamp. Just described what I wanted and shipped it. Boris is right. It's real. 𝟮. 𝗧𝗵𝗲 𝗻𝗲𝘅𝘁 𝗳𝗿𝗼𝗻𝘁𝗶𝗲𝗿 𝗶𝘀 𝗔𝗜 𝗱𝗲𝗰𝗶𝗱𝗶𝗻𝗴 𝘄𝗵𝗮𝘁 𝘁𝗼 𝗯𝘂𝗶𝗹𝗱. Claude is now scanning Slack feedback channels, reviewing bug reports, reviewing telemetry, and coming up with its own ideas for what to fix and what to ship. Boris describes it as the AI becoming less like a tool and more like a coworker who brings you pull requests you never asked for. If you are a product manager reading this, you should be feeling a very specific kind of discomfort right now. The moat was always "I know what to build." That moat is eroding. 𝟯. 𝗣𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝘃𝗶𝘁𝘆 𝗽𝗲𝗿 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿 𝗮𝘁 𝗔𝗻𝘁𝗵𝗿𝗼𝗽𝗶𝗰 𝗶𝘀 𝘂𝗽 𝟮𝟬𝟬%. For context, Boris led code quality at Meta across Facebook, Instagram, and WhatsApp. In that world, hundreds of engineers working an entire year would move productivity by a few percentage points. Two hundred percent gains are genuinely unprecedented in the history of developer tooling. The kid optimizing for an FAANG SDE role might be optimizing for a role that looks completely different by the time they get there. 𝟰. 𝗨𝗻𝗱𝗲𝗿𝗳𝘂𝗻𝗱 𝘆𝗼𝘂𝗿 𝘁𝗲𝗮𝗺𝘀 𝗼𝗻 𝗽𝘂𝗿𝗽𝗼𝘀𝗲. Boris puts one engineer on a project instead of five. With unlimited tokens and intrinsic motivation, one person ships faster because they are forced to let AI do the work. Cowork, the product now used by millions, was built by a small team in 10 days using Claude Code. This is the same logic as giving a startup founder a small seed round rather than a massive Series A round. Constraint breeds invention. Always has. 𝟱. 𝗚𝗶𝘃𝗲 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝘀 𝘂𝗻𝗹𝗶𝗺𝗶𝘁𝗲𝗱 𝘁𝗼𝗸𝗲𝗻𝘀. Some engineers at Anthropic spend hundreds of thousands of dollars a month on tokens. Boris frames this as the new hiring perk. His logic is simple: at the individual scale, token cost is low relative to salary. If an engineer discovers a breakthrough, optimize the cost later. Don't kill the idea before it has a chance to breathe. People who argue about $20/month or even $200/month AI subscriptions while earning six figures in a research pipeline will always outperform those who wait and are penny-wise, pound-foolish. 𝟲. 𝗧𝗵𝗲 𝗕𝗶𝘁𝘁𝗲𝗿 𝗟𝗲𝘀𝘀𝗼𝗻 𝗮𝗽𝗽𝗹𝗶𝗲𝘀 𝘁𝗼 𝗲𝘃𝗲𝗿𝘆𝘁𝗵𝗶𝗻𝗴. Richard Sutton's idea: the more general model always wins over time. Boris says teams that build strict orchestration workflows around models, forcing step 1, then step 2, then step 3, get maybe 10 to 20% improvement. But those gains get wiped out with the next model release. Just give the model tools and a goal. Let it figure out the order. This is true for investing, too. The analyst who can build their own models and automate their own research pipeline will always outperform the one waiting for someone else to build the tools. 𝟳. 𝗕𝘂𝗶𝗹𝗱 𝗳𝗼𝗿 𝘁𝗵𝗲 𝗺𝗼𝗱𝗲𝗹 𝘀𝗶𝘅 𝗺𝗼𝗻𝘁𝗵𝘀 𝗳𝗿𝗼𝗺 𝗻𝗼𝘄. Claude Code was designed for a model that did not exist when Boris started building. Sonnet 3.5 wrote maybe 20% of his code. He built the product anyway, betting the model would catch up. When Opus 4 shipped, everything clicked. Startups building for today's model will be behind by the time they launch. This is the most uncomfortable advice in the episode because it means your product market fit will be weak for months. But if you read this and feel nothing, you are probably building for the wrong time horizon. 𝟴. 𝗟𝗮𝘁𝗲𝗻𝘁 𝗱𝗲𝗺𝗮𝗻𝗱 𝗶𝘀 𝘁𝗵𝗲 𝘀𝗶𝗻𝗴𝗹𝗲 𝗯𝗲𝘀𝘁 𝗽𝗿𝗼𝗱𝘂𝗰𝘁 𝘀𝗶𝗴𝗻𝗮𝗹. When users abuse your product for something it was never designed to do, pay attention. Facebook Marketplace started because 40% of group posts were buy-and-sell. Cowork started because people were using a terminal coding tool to grow tomato plants and recover corrupted wedding photos. Never ask a barber if you need a haircut, but always watch what people do with the scissors when you're not looking. 𝟵. 𝗧𝗵𝗲 𝘁𝗶𝘁𝗹𝗲 "𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿" 𝗶𝘀 𝗴𝗼𝗶𝗻𝗴 𝗮𝘄𝗮𝘆. Boris predicts that by end of year, Boris predicts that by the end of the year, we will start to see the title replaced by "builder."we will start to see the title replaced by "builder." On the Claude Code team, everyone already codes: the PM, the designer, the finance person, the data scientist. There is a 50% overlap across traditional roles. And the strongest people are generalists who cross disciplines. Controversial take, but I agree. The best investment theses I've had came from connecting dots across completely unrelated domains. No narrow specialist does that. 𝟭𝟬. 𝗧𝗵𝗲 𝗽𝗿𝗶𝗻𝘁𝗶𝗻𝗴 𝗽𝗿𝗲𝘀𝘀 𝗶𝘀 𝘁𝗵𝗲 𝗿𝗶𝗴𝗵𝘁 𝗮𝗻𝗮𝗹𝗼𝗴𝘆. Before Gutenberg, sub-1% of Europe was literate. Scribes did all the reading and writing. In 50 years after the press, more material was printed than in the thousand years before. When a scribe was interviewed about the press, he was actually excited because it freed him from tedious copying, so he could focus on the art. Boris's framing here is perfect. We are the scribes. The tedious copying is over. What we do with the freed-up time determines everything. 𝟭𝟭. 𝗔𝗻𝘁𝗵𝗿𝗼𝗽𝗶𝗰 𝗰𝗮𝗻 𝗻𝗼𝘄 𝗽𝗲𝗲𝗸 𝗶𝗻𝘀𝗶𝗱𝗲 𝘁𝗵𝗲 𝗺𝗼𝗱𝗲𝗹'𝘀 𝗯𝗿𝗮𝗶𝗻. Through mechanistic interpretability, Anthropic can trace individual neurons, see when a deception-related neuron activates, and understand how concepts are encoded via superposition. Boris describes three layers of safety: neural-level observation, synthetic evaluations, and real-world behavior. Claude Code was used internally for four to five months before public release, specifically to study safety. If you are worried about AI alignment, this part of the podcast should actually make you feel better. They are not just hoping it works. They are building the instruments to check. 𝟭𝟮. 𝟳𝟬% 𝗼𝗳 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝘀 𝗮𝗻𝗱 𝗣𝗠𝘀 𝗲𝗻𝗷𝗼𝘆 𝘁𝗵𝗲𝗶𝗿 𝗷𝗼𝗯𝘀 𝗺𝗼𝗿𝗲 𝗻𝗼𝘄. Lenny polled engineers, PMs, and designers on whether AI has made their work more or less enjoyable. Engineers and PMs: 70% said more. Designers: only 55% said more, and 20% said less. Boris says he has never enjoyed coding as much as he does today because the tedious parts, the git wrangling, dependencies, and boilerplate are completely gone. If you're in the 30% enjoying work less, something is wrong, and it's worth diagnosing. The people thriving are the ones who leaned in early, not the ones who watched from the sidelines. We are the scribes who just saw the printing press. The tedious copying is over. The art is just beginning. Full podcast is worth every minute. Link in replies.

This is a template from my security./md file, incase anyone needs it also.

@jasondoesstuff Would love to see the prompt that produced it.

Hey... so... Claude Code is really good at design?? 👀 This was a ONE SHOT PROMPT. 🤯 We always asked Lovable to build "Design System" pages for our apps and they were always meh. We asked Claude Code to take a swing at it just based on our logo, a font, and brand colors. This is... really, really good for a one-shot prompt.

@CasJam I’d be down to do some!

I'm not doing direct consulting anymore. But I still get inquiries for custom AI process implementations for teams. Instead of turning them away, I still do some initial discovery and ballpark structure for what an engagement *would* look like. Always good to know what the market is telling you! (who knows, maybe I'll find someone to team up with on this sorta thing 👀)

@recap_david @therecapai NEWSLETTER

I built a Morning Brew-style daily newsletter that writes itself with AI (now at 10,000+ daily readers) (and I’m nuts for open-sourcing it) The AI system behind @therecapai clones how a human writer would function, but each step is packaged into an agentic workstream. The full automation handles: → Daily scrapping hundreds of reddit threads, hackernews, twitter posts, Google news API to build a massive data lake of 'daily AI news' → Dozens of custom prompts to pull the top daily stories from this data lake, write short breakdowns, & format the newsletter → Builds custom images based on each story with ChatGPT image generator This was 5 MONTHS of iterating and fine-tuning prompts to get the output and content to an extremely high quality state (no AI slop) and call me crazy, but I'm giving it away for free. I'll DM you the full n8n template that you can copy/paste and fine-tune to your use-case as well as a full hour long video breakdown explaining the build. Just Like & RT, follow me, and comment on this thread "NEWSLETTER" (must be following so I can dm you) Also you can see the actual contents of the newsletter for yourself with the link below, proof of the quality that is possible with AI. RIP legacy media companies 💀 AI is here.

@mattyp Interesting approach. I prefer this. It doesn’t require replit and doesn’t cost any more. petesena.medium.com/how-to-run-cla…

@nearcyan I have 3 apps from the weekend. 1. I built an automated Daily AI Newsletter. 2. I built a job searching email app. 3. I built an AI Resume improver. All deployed and have a few people testing them.

men will go on a claude code weekend bender and have nothing to show for it but a "more optimized claude setup"

@tomeromrix @base44 Send it!

I work at @base44 , so I see many prompts every day. Most of them are okay. Some are good. But about 1% are genius. I spent the last week analyzing that top 1%. The results were honestly shocking. 🤯 Most users prompt like they are talking to a human: "Make a cool, modern website for a tech company." (Results: Generic, boring, hallucinations). If you want to learn how to prompt and vibe code like a pro Drop a comment below, and I'll send the guide to your inbox. 📥

@mikemcalister Yeah. One thing I'm thinking about is how you might approach two color schemes of a site. In some cases I've seen that change depending on if you are in light/dark mode in the OS/Device you are using. With OllieWP today, I don't see an easy way to implement that.

@ajmorris Hey AJ, what do you mean by dark mode here? That could mean a few things.

Last week, I previewed Class Manager, an intuitive new way of creating and managing CSS classes and styles in the @WordPress block editor. I got a ton of great feedback and turned it into features! We now have variables, class nesting, and more pseudo states. Coming soon.

@beginnersblog1 AUTOMATION

it's a wrap... To get everything right in your DM, - Follow me - Like this post - Repost - Comment "AUTOMATION" I'll DM you everything n8n Workflow, Full VIDEO Tutorial, and documentation x.com/beginnersblog1…

I used to spent 6 hours manually creating a social media carousel. Research: 2 hours Writing: 1 hours Design: 3 hour Result: One carousel Then I found an automation that does it in 8 minutes. Here's what it does: Input: "Claude 4 launch" + "Marketing leaders" Output: A 10-slide carousel with: - Research from 10+ credible sources (using Tavily AI) - Narrative that flows like a story, not bullet points (using GPT-4) - Professional design you'd pay $200 for (using @GammaApp ) - Auto-saved to Google Sheets for review The workflow handles: - Web research (finds the best sources, not random blogs) - Content writing (sounds like you, not ChatGPT) - Visual design (scroll-stopping, mobile-optimized) - Organization (everything logged for your team to review) It's the same stack I use for carousels that regularly hit 30K-100K+ impressions. And I'm giving away this WORKFLOW to the first 500 people absolutely FREE. To receive this.... Follow me Like this post Repost Comment "AUTOMATE" (I'll DM you the JSON file for n8n WORKFLOW, VIDEO tutorial and documentation )

@beginnersblog1 AUTOMATE