I thought of this after a recent bug I found. I use Vivaldi browser and recently it updated. After the update my mouse cursor was not visible when within the browser window. Other programs worked fine. I tried visual studio and steam and epic game store all had my mouse, Vivaldi didn’t.
I closed all instances of Vivaldi via task nanager(was unable to click the x) and restarted it. That fixed the bug and I haven’t been able to replicate so I don’t have anything to submit for a bug report. Just a really strange thing.
What have been your weirdest bugs?
It’s not a bug per se, and we’re gonna see a lot of this moving forward.
Did a code review, hefty code review, and as I got to the end of it where “the magic happened” I discovered that the logic was actually a case statement for every permutation.
Because they’d asked the AI to write logic to go through each type, the AI wrote a case statement for EACH TYPE.
… it was so fucking fast though. So wrong but so so fast compared to the actual running code.
deleted by creator
Fast to run or fast to make?
I’m a big fan of if it’s stupid but works it’s not stupid, especially if you get a runtime speed improvement.
Yeah it might be theoretically difficult to make an update but if by “each type” you mean like the primitive data types (string, int, char etc) I doubt the language is going to change how, for example, an int works. If you they do so many programs will break.
It ran super fast but only over that one constrained input, it didn’t allow for new use cases.
Ah ok, i was thinking you meant the previous solution was so complicated so the basic switch sped it up
The LLM basically just did the work once for the sample data set, so all the computation happened up front.
If that was the only data set we’d ever need, and the data set didn’t change realtime based on sensors then … hell yeah that gross switch woulda worked 😂
Ah ok… That makes sense. I was thinking like generate a stream of data, data comes in some format like (string dataType, float dataValue) and a switch like case int{do this} case string {do that} then get new data and repeat while(true).
If it only was calculating based on the test case yeah that’s bad.
I told this before but I had a project which had an xml configuration of many sections each targeting something different. I wanted each section as an object. This was a system of many combined systems like one dmm, one custom automated shield box, one bluetooth tester, etc. Each needed specific data to connect to it and configure it for the tests we wanted to run. This was all I needed in the xml file.
So I coded 1 function to read 1 section of the xml file and map it to an class object. I then copied that into Ai, copied configuration file into Ai, and told it to replicate it for each section. That worked. I think Ai can be used in specific circumstances where you are doing like repeated operations but it gets grossly overused. You also have to know the domain and the language to understand what it’s doing.
Another example is I was asked to make a sql query which was basically a join(serial number and test guid in one table, test guid and test results in another table and only given serial number). My boss sent me a list of like 150 serial numbers separated by spaces over teams. I wrote the query for the first one and told the Ai to replicate it on the other serial numbers. Yes I could of gone through the list, backspace the space, add common, press enter and repeat. I knew how the query worked. I know the domain I was working in. The Ai output was basically the same as my original just with more serial numbers in the where clause.