youre-wrong3

It’s very useful outside of programming. Keeping human in the loop makes outcomes better. But regardless ai is a huge productivity boost.

> However often the best way to handle grunt work is to write better abstractions, something AI sucks at.

If you checked out of ai in 2023 then this is true. It’s simply not true anymore. If you struggle then it’s a skill issue not an AI issue

> At the level of complexity I work at, it's (often) faster to just code it myself than to expect AI to converge on a result I like and then hand check it.

Would love an example because no one has ever been able to give a coding example that AI isn’t helpful for. I had one person on linked in try claim their undocumented audio hardware won’t work with ai but when we got ai to probe it and build docs it ended up solving a bunch of complex bugs they couldn’t fix.

No. You can absolutely build things with AI small or large and understand it. If you don’t understand it. Then you’re not caring about the output to begin with and not guiding it to build the solution you want.

People seem to ignore the fact that with MCP you can serve up the tools the user wants and has access to instead of a rest api doc specifying every endpoint and bloating the context.

Seems like a lot of people who aren’t very good remain skeptical.

I don’t like it. Structures responses really do not work well with LLMs at all. They are one of the biggest causes of issues with tool calling right now.

So were Microsoft employees until they got forced to use copilot. Everyone seems to think MS got rid of Claude Code due to cost but it had nothing to do with cost. Employees weren’t even using copilot. Can’t make a product better if you don’t use it. Meta should be the same. Use your own product.