Joe Muoio

Joe Muoio

@joemocode.bsky.social

Former Senior Software developer at Amazon turned freelance helping small businesses automate and building AI software for people. I like games, gardening, ceramics, and food. Words are mine and not from a transformer. https://blog.joemocode.com/

30 followers45 following56 posts

Pretty crazy to see so many articles talking about issues of “AI“ that are really just about the private credit crunch. Case in point: www.reuters.com/business/bla... So Fink says we all need to buy equities. ignore the fact that wealthy folks have more so it doesn’t actually help inequality…

reuters.comBlackRock's Fink warns AI boom could widen wealth divide without broader participationAsset management giant BlackRock's ​CEO Larry Fink warned on Monday the artificial intelligence boom risks widening the wealth gap unless more individuals share in ‌market gains.

Yes market participation is good. It will help you. It will not help inequality. Does ai make it worse? To be determined. But there’s no substance in the article that shows that. Corporate failing to realize benefits of ai than an individual can have.

Yes! Web components' time to shine! They are excellent for truly modular and independent front end components. Also excellent as a design system lib since they work with every framework. ..but, where is SolidJS on this list???

Justin Fagnani@justinfagnani.com

Nice result in @zeroheight.com's 2026 Design Systems Report: report.zeroheight.com#your-tools Web components are the second-most used "framework" among the respondents. This makes sense: if you build web components you support all the frameworks. Otherwise, you'd probably only support React.

Wondering how other's juggle multiple CLI LLM client sessions. I will frequently have sessions: 1) planning work (assuming current task is not too cognitively heavy), 2) implementing features from a plan 3) fixing bugs 4) fixing tests/build issues How do yall use claude code?

View full thread

This is my max number of active sessions. It's tough to work on future features 1. because I need to sandbox or set up multiple repos and keep them in sync (do you do this?) 2. It just becomes too overwhelming for my squishy brain to keep up with all the changes and context switching.

Been thinking to create a review specific skill or slash command with my and my teams' practices/code philosophy outside of things that can be caught with a linter. Any tips for doing this?

Wondering how other's juggle multiple CLI LLM client sessions. I will frequently have sessions: 1) planning work (assuming current task is not too cognitively heavy), 2) implementing features from a plan 3) fixing bugs 4) fixing tests/build issues How do yall use claude code?

None of them have custom prompts or skills or anything. If I do happen to use a skill, that's likely it's own session. Also will start a fresh session to review code before reviewing it myself by hand. Just to give initial feedback without the bias of the plan in context (for better or worse).

I gotta write an updated blogpost on my use of AI in 2026. The short is that I have embraced throwaway software. It's become so much easier to prototype ideas and to build simple programs for testing something. And for long term projects, the basics of software development are unchanged.

Opus 4.6 is finally a big model that changed my workflow. Moreso the agent harness. I've leaned into that more for serious work. New problem: reviewing the massive amount of code produced in one agent shot at a relatively high quality. It's never 100% right. I still use human-in-the-loop too.

Trying a new Claude Code technique with Opus 4.6. Wrote a detailed plan with my constraints with Claude formatting it for "future Claude". Created a slash command that takes a plan document with instructions to spawn sub agents with instruction to surface ambiguity to me instead of assumptions.

Done phase 2. Onto Phase 3. Gonna take 100X as long to review this as it takes to write 😅 Let's hope all my refactoring work for better code structure and the upfront planning paid off...

Every time I go "full vibe code" It doesn't work great if I need to maintain that software. While I can 10x productivity on initial prototype, Claude code seriously degrades without proper structure and planning. So I end up spending days refactoring the mess I created.

View full thread

LLMs really boost your productivity when you know what you want, and really hamper it (long term) when you don't. This project involved a lot of experimentation and I probably should have reached for something easier to iterate with in the first place :)

I will add, the main issue with my vanilla system was not the tech choice, per se, but the cruft left about from my experiments that was silently sitting there, occasionally failing at runtime. Left a lot of traps for the AI to run into. SolidJS made these problems more apparent.

Every time I go "full vibe code" It doesn't work great if I need to maintain that software. While I can 10x productivity on initial prototype, Claude code seriously degrades without proper structure and planning. So I end up spending days refactoring the mess I created.

Learned this lesson again. Coming off a week of refactoring some frontend code from KitaJS serverside templates + vanilla HTML, CSS, and TS to instead use SolidJS + Tailwind (kept KitaJS). Needed to orchestrate state of up to 1300 different data calls and it was too error prone with vanillaJS.

Quite happy with #SolidJS and #TailwindCSS. First time using them. My features are once again easy to add and iterate on. But took 8-10 full claude code sessions + more for planning the work. Had to really take a step back. Backend code where I thought things through needed very minimal work.

Going to be posting over here more than Twitter. Starting from scratch on the followers list 🤠 I'm Joe. I'm a Software Developer with over a decade of experience (primarily Amazon). I now help small businesses build software and make decisions around software. I like food, ceramics and games.

You are up to date.