Comments by "muh diversity" (@muhdiversity7409) on "" video.

Software Engineering is not about writing Leet Code. If it was Google wouldn't be canceling so many projects and failing to introduce new innovative products, the same malaise exists in so many other corps. They're all jumping on the AI bandwagon because it's current thing so no one wants to be seen as being left behind. Telling everyone that AI will replace actual engineering is just part of that hype train.
2
Speaking of software with bugs. There is an example piece of code that people use as a starting point for OpenCL applications. Depending on your environment the OpenCL compiler will fail telling you there's gibberish in the input. I've seen many posts about this with no good answers other than "it works for me". Turns out that if you have certain kernel mitigations turned on that scrub memory then you're likely to see the example programs work. Why? Because the original program assumes that the buffer the OpenCL code is written into is zero terminated and there's an off by one bug that ensures the buffer is never properly terminated. Get rid of the developers because I'm sure that AI will totally be able to figure things like that out. People that say the AI will replace software engineers are living in a Utopian fantasy land.
1
@InternetOfBugs Absolutely. I figure it out because the application was working. I was experimenting with something and turned off all the kernel mitigation and over a month later I started the app an it would crap out. I started to look at the code more closely and the complaints on SO, which didn't have an answer, and then asked myself what has changed? That gave me a clue that the OpenCl compiler was reading beyond the buffer bounds. I did feel a little proud of myself once I re-wrote the reading code and the change fixed the issue.
1