I'm under a guy that just manages 20 or so doors now and he's a good dude, but I have to wait a longer time, generally, like when my heat wasn't working at the beginning of the winter and his plumber had the flu. Luckily it wasn't bad weather yet, but I definitely felt the potential for strain.

I imagine this is the kind of thing you see at a large company where a good chunk of people are just coasting by doing nothing, Nelson Big Head style.

I think we've all worked with someone who (I imagine subconsciously) feels the need to make things longer without actually adding more information in there, and it just makes everyone's day a little harder.

Looks like Wispr Flow uses a cloud model [0]:

> Cloud based speech processing infrastructure for 1B users

It gets to be a messy comparison because my iPhone can do STT with no latency pretty well fully on device, but Wispr Flow requires a cloud model, but to be fair, older Apple devices do as well. It's not an apples and oranges comparison, but I think those technical details make this a non direct comparison in a few ways.

For on-device with low system resource usage, Apple's is pretty damn good.

[0] https://wisprflow.ai/post/technical-challenges

These things are so tricky because everyone has a seemingly conflicting experience. Part of the fun I guess!

We started working on a new product a few months ago and it's really dangerous up front on an empty code base. It can quickly write more code than you can comfortably understand. The more serious danger is when three people are all doing that at once. I had to bring this up at meetings and try to get a better review culture going.

Now that we're a few months in and changes are more targeted additions to an existing system we're happy with, it's _huge_ (which has been my experience on our existing product). I can drop a brief paragraph I speech-to-texted into my agent, give it a general starting place (where I imagine the issue/feature extension point is), and then tell it to do some research and propose a change. I'd guess it's about 50% of the time that I have to update it's implementation plan. Then I let it run (my favorite is setting this up before a meeting) and come back. Then we have to review the code and go from there.

Definitely a 50%+ speed up in some cases, but not all. It's also great for problems that procrastinating, as it reduces friction so much.

I have to imagine the Obsidian team is going to respond seriously to this and I look forward to seeing what they do. They have my full confidence. I'm surprised the system was initially designed as it is without those better permissions and sandboxing, though.

Seriously though, I agree with your sentiment that community plugin security can and needs to be improved, but how does someone saying they use it every day "disregard software usability as a formal discipline, along with decades of UX research and standards"

As for sherlocking, this is such a minor use case that I'm not sure why anyone (minus maybe the initial app developers) would be upset. As a user, I need one less app to do something (that I should've been able to do for years). It's not like they're stripping an ability away from developers to hide it behind their own gates.

The way I'm interpreting this is that it's a way to abstract stagnant QR or barcode passes for smaller businesses and libraries. We'll see at the WWDC though.