I'm much the same way. Every single time I've early adopted, I've been bitten for having done so. I have this seemingly rare skill where I manage to find all of the obscure, random bugs/issues that no one else else runs/ran into. The more obscure it is, the more likely I'll run into it. If I early adopt, I not only run into those bugs, but I also manage to find the hundreds of other bugs that everyone else runs/ran into as well. It's never a pleasant experience because I'm the type of person to file detailed bug reports, track down the cause to the line of code, and suggest a couple of fixes, so I usually just wait a while to avoid that pain and suffering.
On the upside, being a later adopter is also more budget friendly. What cost $250 at launch is just $50 or less two years later and has fewer bugs/issues too thanks to applied bug fixes. So you get to save thousands of dollars that you can put to use on a greater quantity of higher quality items (hardware, software, goods and services) when later adopting.
Just as an example of a weird, obscure bug. I recently ran into a bizarre issue with Windows 10 where after about 90 days of system uptime, the icons in Task Manager Details tab suddenly go "wonky." The OS starts displaying random icons from the icon cache for each running process or even no icon at all. I can't find anyone else who experiences the problem because, for most people who run Windows, Windows automatically updates long before 90 days is up. I'm at 142 days of uptime right now. Would rebooting "fix" the problem? Sure. For about 90 days. The real concern is that this bug might be exploitable. How does a corrupted OS application icon cache happen in the first place? If it's due to a buffer overflow somewhere, then some code could trigger privilege escalation and might even be remotely exploitable (e.g. via favicons in the web browser). See what I mean though? This is the kind of bug that only I seem to run into. The sort of stuff that no one else has paid much attention to even if they have run into it themselves but didn't think twice about it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm much the same way. Every single time I've early adopted, I've been bitten for having done so. I have this seemingly rare skill where I manage to find all of the obscure, random bugs/issues that no one else else runs/ran into. The more obscure it is, the more likely I'll run into it. If I early adopt, I not only run into those bugs, but I also manage to find the hundreds of other bugs that everyone else runs/ran into as well. It's never a pleasant experience because I'm the type of person to file detailed bug reports, track down the cause to the line of code, and suggest a couple of fixes, so I usually just wait a while to avoid that pain and suffering.
On the upside, being a later adopter is also more budget friendly. What cost $250 at launch is just $50 or less two years later and has fewer bugs/issues too thanks to applied bug fixes. So you get to save thousands of dollars that you can put to use on a greater quantity of higher quality items (hardware, software, goods and services) when later adopting.
Just as an example of a weird, obscure bug. I recently ran into a bizarre issue with Windows 10 where after about 90 days of system uptime, the icons in Task Manager Details tab suddenly go "wonky." The OS starts displaying random icons from the icon cache for each running process or even no icon at all. I can't find anyone else who experiences the problem because, for most people who run Windows, Windows automatically updates long before 90 days is up. I'm at 142 days of uptime right now. Would rebooting "fix" the problem? Sure. For about 90 days. The real concern is that this bug might be exploitable. How does a corrupted OS application icon cache happen in the first place? If it's due to a buffer overflow somewhere, then some code could trigger privilege escalation and might even be remotely exploitable (e.g. via favicons in the web browser). See what I mean though? This is the kind of bug that only I seem to run into. The sort of stuff that no one else has paid much attention to even if they have run into it themselves but didn't think twice about it.