As with anything. Either you can go full-speed without much understanding and hit a wall when you need to understand stuff or you can go a manageable speed and actually understand the codebase.
I don't think we can do both. The difference is that it's optional now depending on the project and the audience.
> You can never ask why a model did a certain thing
Of course you can! It might be following outdated docs or read something in legacy code and tried to follow that pattern and it'll tell you as much if you ask it in a way that actually gets you the reason instead of it thinking it needs to immediately fix the mistake.
I dunno about this. Agent discovery is needed, yes. But I don't trust the tech companies right now to do this in a privacy preserving manner. I feel like it'll be used to collect all sorts of data not intended for the parties. Even in the flight ticket example, a third-party insurance or ad-tech company could listen to the request for ticket prices and determine intent to travel (including destination and dates).
I use Conductor's spotlight (and a Pi extension I derived from it) but it's not perfect. Once a migration executes, I'm pretty much bound to it but at least once, I have just backed up the database before switching and then restored that.
Looks like a useful tool but I don't know anything about construction.
Love the transparent AI helper implementation though. I feel like you don't even need to say it's AI because it's so helpful but not in your face but maybe that's what people are searching for.
> keyboard/shortcut situation is absolutely cursed. Not different...actually cursed
You know, you can change almost any shortcut you want with Karabiner (app). You don't even need to memorize them.
When I first switched to Mac after using Ubuntu for 4 years before that, I didn't expect this level of customization. It's misunderstood because Apple doesn't advertise this.