jownz

I totally understand why George is upset. Troubleshooting crashes within a vendor's closed source product is one of the most painful things I've had to do professionally. In my case, it took months of patience and collecting pcaps to finally get it resolved. George doesn't have months.

I've been fascinated by his live streams where he has been digging into the bug himself: https://www.youtube.com/@geohotarchive/videos

As crappy as the situation is, I must say it's been great to see George's passion to solve these types of technical puzzles reignited! It seems like he's tried his hardest to work with AMD in an nonabrasive manor but he has become very frustrated by the lack of progress.

AMD would be wise to just pair one of their best, whom has access to the source, with George for just a couple days.

...I think I'm in love.

I'm a Pet Detective, and I currently make $60,000 in Miami. I'm ONLY interested in jobs as a Sr. Pet Detective that pay at least $60,000 in The Bay Area.

This made my day.

glassdoor.com?

config.sys

I was thinking the same thing! I wonder if the asker ever thought to talk to the A? Maybe he's ticked off because he's had to fix countless careless bugs produced by the 'B's for the past year? Maybe his salary isn't up to par? Maybe he's not pleased with architectural decisions? Maybe his 'nix box was pwned last night? The best way to fix an A is to talk to them. A happy A is worth 10 'B's. 'B's produce redundant and infuriating sloppy code. Most 'A's are self-taught for the most part and they play very well with people on their level.

Master Blaster ain't horrible.

Ego boostin' - I could definitely solve that bug that's been lingering around like a bad fart listening to this.