Everyone feels behind. The truth is that every company is different. There are companies out there that are almost certainly moving faster than you. There are also plenty of companies out there just getting started. And truly nobody knows what they’re doing (everyone at the edge is making it up as they go along). Most likely you’re in the big messy middle along with almost everyone else. It’s okay. Take a deep breath. And then get to work. - Feeling behind is a great motivator. It’s a simple truth that you _can_ be doing more. - You will not stop feeling behind by being conservative, or by doing things the way everyone has gotten comfortable doing them. - You do not need to operate like Anthropic overnight, but you also need to stop operating like you did 12-24 months ago. Choose a small experiment to run with your operating model. One week, or a few, of doing things differently. Permission to flout the norms (at least the ones that won’t get you in regulatory trouble). Take stock of what worked and what didn’t; rinse and repeat. The important thing is not where you’re at today. It’s how willing you are to adapt and change.

Like everyone, I've been playing with video gen. My latest experiment → turning reference whitepapers and training materials into little vertical videos for teaching clients. This one is our @cxodev guide to useful architecture patterns using jev + other decision models.

@sidharthkmenon The edge cases are all handled comprehensively, it always tries at least two prototypes if not more before settling on the best design, which I never did, it has very rigorous pre-commit reviews, it runs a ton of microbenchmarks & mutation testing. It writes better code than me.

Excited to be a @SpaceXSI launch partner to help your team put @bot, grok, and @cursor_ai to work inside your technical teams (or your whole company.) Want to see where we can help? Try our AI readiness assessment →

I also hacked a cheap smart frame and: - Chose a different frame to get white and save myself $5. Low sample size but I'm half convinced you could choose any frame? - Used codex instead of claude code - I had a much easier time than @clairevo 😂 - Spent like 30 minutes and had something I was very happy with - Hardest part was finding a usb-c to usb-a dongle in my house so I could connect my macbook to the frame - Did not record a video - Would highly recommend the instructions at makes it so easy

I strongly disagree with the "AI is going to kill UIs" prediction. But I do think there's lots of stuff I never want to have to do through a UI again, and I think agents will inevitably impact what kinds of things get prioritized in UIs. This from PostHog is pretty close to how I'm feeling right now. I'm building something new where lots of stuff is driven by agents, but I'm still devoting a lot of time to the UI to make it easy to understand, review, steer, and undo that agent work.

Everyone 9 months ago: Gas town is crazy! Mayor? Polecat? Who wants to manage all this stuff? Everyone today: Well I had my first mate talk to the captain of the ship, who pointed us north. Then the first mate had all the sailors swab the deck for 2 hours. Anyways, that's how we rebuilt Salesforce in an afternoon.

Cringe Bot is a team Grok Bot I created to find small problems with the stuff we build that makes our eyes twitch a little. It runs automatically 3x a week, does its own QA, and drops up to 5 findings per run with threaded screenshots. It runs against our "marketing" website ( the custom app we built for our course, and a few other things. I take a quick look at the findings and have @DevinAI investigate and put up PRs for most of them.

At @cxodev we like to talk with clients about the need for AI "transformation" rather than AI "adoption". Transformation conveys a degree of change that adoption alone does not. Far and away the most common pitfall we see is teams adopting AI tooling but not changing the way they work. It's hard to get real change out if you're not putting real change in. @levie calls this "process reengineering"; changing workflows to take advantage of AI rather than "just layering on agents into the existing flow". It's a great name, and it's worth examining whether your approach to AI fits this moniker. We believe that the engineering function is a great place to start AI transformation. Because of the highly verifiable nature of software development, as well as the fact that models are very good at writing code, if you can't transform the way your engineering team works with the current tools, you're going to have a hard time doing it anywhere else. And also, you're going to learn a ton from making agents successful in your software development lifecycle (SDLC), or perhaps making your SDLC successful with agents, that can be applied to other functions as well. That last point, that maybe you need to adapt your SDLC to agents instead of the other way around, that's process reengineering. Other functions within your company probably don't have anything nearly as well defined or obsessed over as the SDLC. But I assure you there is a process lurking in there, waiting to be reengineered, and that's where you're going to find real leverage. The most AI-forward companies aren't just adopting tools broadly, they're using what they learned from reengineering the SDLC to rethink processes and workflows across the organization around the joint capabilities of humans and agents.