890 karma · joined April 14, 2017
history|grep 'git commit'|wc -l
is 20 times larger than history|grep 'git push'|wc -lI've encountered a case when it does matter. I tried applying for a bank online through multiple browsers, OSes, VMs, but never managed to get the form to work. Eventually I called them to apply - there was a valuable perk for me - but most customers just won't bother. A good software team would have spotted the drop in conversions instantly.
I told them about it, using the terrible online form. They weren't interested.
I doubt it would work, power users turn off tracking. Presumably you can't trust that the tracking will return only what they say it will (and not your internet history) but you can trust that opting to turn it off will turn it off.
On this note: if you opt-out of telemetry, don't complain when your power-user features stop being catered to.
Most bugs I create are for simple reasons and can be found by scanning the first error logs. If I add print statement debugging because I couldn't then they'll often be adapted into additional logging. If I use a debugger for this as my first tool and don't add logs, I'll have to do it again next time, too[1].
If the bug is not a simple one and is not a structural bug, there's a decent chance it's something debuggers deal with poorly: data races, program boundaries, non-determinism, memory errors. If it's something that can be found by calling a function with certain parameters, it's a missing test case.
So the times I find debuggers to be worth it are after I've already decided it's a difficult yet uncommon bug. So I use them with despair.
[1] If I fix it with a debugger and then add the logs, I still have to prove it gives the right output when it fails.
This is essentially unfalsifiable. In the case claims about FSD or a person on Mars are wrong then this statement can only be proven wrong when Elon Musk chooses to admit defeat - suffering a significant personal financial loss as a result - or when he retires.
>There's a reason why they were not reviewed widely
Coincidentally, Ferrari also play dishonest games with reviewers: https://jalopnik.com/how-ferrari-spins-5760248
Scaling this to a website that serves people internationally and needs to have a consistent branding is much harder than using an icon.
There is a learning curve, it's just one you climbed when you learned the language (which may not be your own).