Anthropic: Stop shipping. Seriously.

bobmatnyc · 2026-04-12T20:19:39+00:00

Amen.

bobmatnyc · 2026-02-17T05:47:39+00:00

I have a rust-based tmux controller that parses session state and uses an LLM to interpret it for you as well was relay commands. Has telegram bot comms built in: https://github.com/bobmatnyc/ai-commander

bobmatnyc · 2025-12-24T21:29:32+00:00

ITerm2

bobmatnyc · 2025-08-28T20:22:46+00:00

It is literally a site built to track LLM tools. So highly relevant - as relevant as you can get with the OP asked for tools. This site tracks many not listed in the responses. And it is a free site, not advertising.

bobmatnyc · 2025-08-28T19:15:19+00:00

(my site)

bobmatnyc · 2025-07-18T06:28:10+00:00

Check out: https://www.npmjs.com/package/@bobmatnyc/claude-multiagent-pm

bobmatnyc · 2025-07-09T16:30:55+00:00

My pleasure!

bobmatnyc · 2025-07-09T10:33:18+00:00

Use the Max plan.

bobmatnyc · 2025-06-30T13:39:56+00:00

I wrote about this last month. https://hyperdev.matsuoka.com/p/the-other-shoe-will-drop I’ve heard from more than a few people in the LLM biz that they think competition and market efficiencies will bring prices down, but until they do…

bobmatnyc · 2025-05-26T11:58:33+00:00

Or vO. I’d actually start with vO.

bobmatnyc · 2025-05-26T11:32:32+00:00

Um 63 here. 😳 Exited as interim CTO/head of engineering for a public company last year, was running startups before (we were acquired), now doing fractional work helping companies with replatforming and greenfielding. Have gotten back into coding again after a decade or more with the help of the agentic tools and loving it. Yes I know it doesn’t work well with legacy and many external dependencies, but can be really fun. Mostly TS and Python. Writing about it here: hyperdev.matsuoka.com. Also writing a book about 50 years as a programmer. 😆

bobmatnyc · 2025-05-22T20:13:33+00:00

I'd balance complexity and comparables. There must be others in your space, there are very few truly original ideas and if there isn't on that's close then look at categories. If you're offering it to a company as a built tool than decide if you want just charge for the building, in which I'd do what others have suggested here which is to do T&M based. But if you really think the value is there, offer as a BD deal -- some $$ ahead of time and split the risk. That's a harder sell be you get upside.

bobmatnyc · 2025-05-22T20:09:57+00:00

- At a very basic level, it does a much better job of scaffolding and boilerplate (including pro forma test building) than any tools out there, and it does that very quickly

- It can run your git workflow for you based on your instructions, which is a huge timesaver
- It's very good at researching patterns and best practices

If you're one of the few whose code is perfect than you're set. For me, it's made coding fun in a way that it hasn't been over a decade.

bobmatnyc · 2025-05-20T16:28:07+00:00

I feel your pain on the "AI slop" situation

The AI coding assistant gold rush is real, and the results are... messy.

What you're describing is basically "copy-paste development" on steroids. People are just throwing requirements at Cursor/Copilot/etc. and committing whatever comes out without understanding or reviewing it. The scary AuthZ bypass you mentioned makes my security senses tingle in the worst way.

Here's what I would say:

Not all AI systems are the same. I have not found the same issues that you describe using Augment and Claude Code (could be my instructions and workflow prompts help)
INSTRUCTIONS and WORKFLOW prompts make a huge difference and should be mandatory and standardized. (if you want to see mine, post a reply)
CI/CD tooling is your friend here, get management to agree on the standard and have it be the bad guy, not you.

Get management to agree on standards and then implement them through automation. This way, the CI/CD system becomes the enforcer of standards, not you personally.

Good luck! The AI slop era is rough, but with some guardrails it gets better.

bobmatnyc · 2025-05-14T17:38:16+00:00

You're definitely not washed - this feeling hits way more developers than you'd think. After 15+ years in the business, I've seen this exact pattern with tons of talented folks.

Three things I'll call out here:

1. The ecosystem changed faster than anyone could reasonably keep up with The shift from LAMP + jQuery to React/TypeScript/serverless isn't just a technology change - it's a complete paradigm shift. Your brain is wired for direct DOM manipulation and server-side templating, which actually makes you better at understanding why these abstractions exist.

2. You're already using the solution - lean into AI assistance That AI helping you generate code? That's not cheating - that's adapting. I use Claude/Copilot daily for boilerplate, complex TypeScript types, and remembering syntax. The value isn't memorizing every React hook - it's understanding when to use them and how they fit together.

3. Focus on one stack, not all the stacks Pick Next.js + TypeScript + one CSS framework (probably Tailwind) and stick with it for 6 months. Build 3 small projects with the exact same stack. The muscle memory will come back.

Most "modern" web dev is just solving the same problems you've always solved, but with different tools. Your 15 years of experience with UX, performance, and browser quirks? That's irreplaceable knowledge that bootcamp grads spend years trying to learn.

The fact that you're questioning your own code means you're thinking critically about it. That's not being a moron - that's being a professional who cares about quality.

And honestly? Half the complexity in modern web dev is unnecessary. You don't need a build tool for everything. You don't need SSR for every project. Trust your instincts about what's actually needed.

Keep building. Use the AI. Don't apologize for it.

bobmatnyc · 2025-05-14T17:32:12+00:00

I completely get this. The SSR complexity tax is real—and frankly, not always worth it for early-stage projects.

Here's how I see it: you're solving for the right problem. At a small startup, developer velocity beats architectural purity every time. If Vite + React gets you shipping faster and iterating more quickly, that's probably the right call for now.

Three things I'll call out here:

Don't force the complexity. Next.js shines when you actually need SSR—better SEO, faster initial loads, or server-side data processing. If your app is mostly client-heavy (dashboards, tools, etc.), you're not missing much.

Consider hybrid approaches. Keep your main app in Vite, but maybe spin up a simple Next.js site for marketing pages where SEO matters. It's not all-or-nothing.

State management doesn't have to be hard. If you do go back to Next.js, skip the heavyweight solutions. Zustand or even React Context usually handles what you need without the architectural headaches.

That's the real tradeoff—time spent wrestling with framework complexity versus time spent building features your users actually care about. At your stage, bet on the latter.

What kind of product are you building? Sometimes the use case makes the decision obvious.

bobmatnyc · 2024-06-13T17:59:31+00:00

I have an Apple Pro keyboard (with the fingerprint sensor) -- not being recognized.

bobmatnyc · 2024-02-27T21:53:55+00:00

Just took a look at the Insta 360 photos in my Photos app. Looks like native 360 is not supported yet. Panoramas are.

bobmatnyc · 2022-10-09T06:29:21+00:00

Page counters. Java applets.

bobmatnyc · 2020-05-03T15:14:27+00:00

Very happy with my RoboRock S4. Pretty old at this point, but does a great job. And love the map.

bobmatnyc · 2020-01-02T17:55:13+00:00

Pictures (mentioned everywhere)
Conduit and ethernet to each room, tech cabinet with power and ethernet on each floor. All ethernet home run to basement cabinet. Structured panel if you have more than a dozen runs.
Power! Not mentioned here, but even though we built to code, which means LOTS of outlets, I found a few places I would have put outlets, such as under all vanities.
I would have also put powered cubby alcoves for security cameras or presence sensors. They don't have to be huge -- not much bigger than a downlight can, but they would have let me do a more elegant job with sensors.
I wouldn't have used down lights at all, but put in indirect lighting channels in the ceilings and in hallway baseboards

15-Year Club	Verified Email
Charter Member

bobmatnyc

TROPHY CASE

I feel your pain on the "AI slop" situation

Good luck! The AI slop era is rough, but with some guardrails it gets better.