MCP in some harnesses bloats context. MCP in some harnesses doesn't bloat context.
1,205 karma · joined January 27, 2023
MCP in some harnesses bloats context. MCP in some harnesses doesn't bloat context.
Definitely helps that the home assistant api is documented online most likely in the training data.
The ideation of features, their requirements, getting code for features written, testing the features, seeing how they fit in with the rest of the landscape, and maintaining those features. Same as before. Do those go away in your future? Even with the aid of AI agents, do you really think billions of people will want to go through that process every time they want a device to do something? Do you really think the younger generations who are being told AI will replace them will also embrace AI?
Similar to how even your hypothetical devices of the future still very much have an operating system (a kernel, libraries for software to interface with hardware, a standard suite of apps and tools, an environment for the user to kick things off)
> You might as well just say "I think you're overestimating the general public's interest in using computers"
I might, because I think the general public doesn't much like to "use the computer". It's what they need to use for work, or school, or how to listen to music or watch what they want to watch.
We're only just starting the general public's introduction to agentic AI with Siri and some Android devices. I'm betting there will eventually be some horror stories.
Just with the bit I quoted above, that seemed like a big misread of the market and the implications of everyone writing their own apps.
In this future, are people paying the API pricing of traffic providers? In this future, who's supplying the traffic data if no one is using their mapping apps?
> Is there a meeting happening anywhere right this minute that I’m supposed to be in?
> You can go on and on like this. These all sound trivial. That’s the point. They’re normal-life problems nobody would have built serious programs around, because the audience sounds too small.
Waze and Calendars. Both have huge audiences.
Personally I just have presence sensors and eink tablets on the walls.
It's linked multiple times in the article, time stamped and everything.
Like the US of A?
Also various stars have introduced more bottle cap regulations. One such state is a hotbed for inflated software developer salaries.
So, progress?
Any agent with the Home Assistant MCP hooked up can do it fine.
> I hate when UI teams constantly redesign perfectly fine software
... with ...
> Having the UI layer completely abstracted from pre-written code and dynamically generated "on the fly" based on the context of the user is, I believe, the future
In this scenario there's still no guarantee that the UI won't randomly change. There's no guarantee that the ui generated for the user will be the same visit to visit.
Also, gulp / grunt weren't package managers.
> Uploading content deemed illegal by English law (indecent depictions of minors)
Are they relevant questions? I've often commented on lines of code in a PR that "so and so gave me the idea".
> Or how about all the stack overflows I read?
Would be nice to link to them either in a code comment (if they're not changed very much) or again somewhere in the PR discussion
> Maybe I should voice record all the times I swore about Gary the junior dev not documenting something?
If you noticed something severely lacking that would help other people out if that wasn't the case then yes I hope you would bring it up?