fabiensanglard

Oh the irony...

I love this stuff. This is super fun to read.

Also, in the Part 1 thread on HN my comment was "I wonder how they are going to deal with ATI driver stability issues". I guess I got my answer today.

> After this, the kernel panics.

Please elaborate and explain to people with less knowledge why this is bad.

I made a mistake when I researched photos for it and found "one" without sources. You are right this photo looks shady. I have replaced it (with source).

That was an image I found in Google Image search. I should have done a better job to research the provenance and I appreciate being called on it. I have updated the photo.

Thank you for reporting the issue. Fixed.

While the tips are good to handle the volume, I still think this sets code owner on a dangerous path.

AI have limitation and hallucinate. Complex code will be explained in hallucinated way. At some point AI will be unable to write more because the arch has become too complex or the volume of code will be to high.

The article I would like to read would suggest how to force LLM to architect the code like a solid tower instead of a pile of unstable mud.

Quite courageous to go with AMD. I am very curious to see Chapter 2 and how he solves the software stability that used to plague AMD AI applications.

I have completely stopped buying USB. I only rely on thunderbolt cables and hubs now.

What a cool anecdote. I have added it to the article!

I noticed that too but elected to not make it count.

I am ambivalent about this. When I watch the sequence it looks like the guy in the harbor looks at the camera?

This is such a cool anecdote. I have added it to the page!