119 karma · joined December 18, 2021
That's the issue. So many people are burried in their phone or just simply driving irresponsibly for the conditions, these features may be better for them.
As someone who respects the responsibility of driving a vehicle, they're definitely making things less safe in some situations.
I think anyone that can understand a function can understand this, but one might not be happy accepting it's the case, and endeavor to change it.
I think it can be easy to lose sight of that distinction, and eagerness to fix it can be confused with not accepting it could be, but is also probably wrong.
If you are only looking at the call site, sure that could be confusing, but if you are looking at the definition as provided in your post, surely anyone that is able understand the concept of a function can see the problem?
I'm not arguing they don't exist, sure they do, but I'm confused as to how you came up with it as a litmus test? Is it that common?
Surely we can agree in a real scenario renaming it (or fixing implementation to match name) is likely appropriate, but to completely miss the error?
Hope this comes across as curiousity, because I am curious about this one from your list in particular.
I see the externalities and the harm they are and may cause, and at the same time I find it increasingly difficult to avoid using LLMs as there is personal value to be extracted. Further, so many others are using LLMs to pump their productivity numbers (reality may differ and time will tell) its hard to keep up without using LLMs.
Obviously the stakes are lower, I still review code before making a PR, but the exhaustion from getting there is similar.
Huh?
We're dragged into this kicking and screaming and yet normies think we're the crazy ones.
I'm essentially along for the ride because the masses will gobble it up.
I completely agree, but as a user I'm the victim of the developers choice.
Not exactly the word I'd use, since it really hasn't changed since VB4, but it's definitely reliable and stable.