sumtechguy
Joined 6 years ago
Joined 6 years ago
I personally am a close the whole browser out at the end of the day guy. With bookmarks for things I just have not got to yet. With a every few months cleanup of the 'to do' folder. Just today I have probably opened 20 tabs and closed 15 so far. At the end of the day they should all be gone.
I have been having a different exp with it. Those are even more important. These things are creating some wild code. Then sticking to its guns in some cases and just rewriting the same bug over and over.
Just this week I literally showed the thing where it was breaking. I wanted it to trace where the error was coming from. Instead it immediately wrote guard code and patted itself on the back. Not a bad idea but does not give me the reason of why something was broken. As where it broke is just part of the problem. Turns out I had a data issue. Guarding the error was the wrong plan in what I was looking for. The user needed his data fixed. Without tracing and debugging I am pretty sure AI would not have found it. Not without me prompting even more. It had twisted itself silly trying to make the error good instead of root cause. Took me an hour or so before I realized it was doing that.
Trust by verify. These things make all sorts of assumptions unless you are very accurate in your prompts.
totally. I spent yesterday trying to get an AI to make a test case for a very specific bug I had. It kept telling me that it had it. When I could clearly trace thru the code and see it did not. After about 5-10 rounds of that I just wrote the test myself. But at least AI helped with all of the dumb cruft that went around it.
But if I did not know the domain I may have easily just said 'yep looks good'. AI on the other hand saved me at least 3-4 hours of writing all of the scaffolding that made it easier for me to check. In the end the bug had nothing to do with the test. AI did not find that. I went back point by point of what changed in the code and found where I had messed something 2 weeks ago.
A few months ago it seemed like it would not do this. Now in the past week I have come across 3 different ones that did something similar. Just 'stuck' in a local maxima and getting the AI to go around it is a pain. This is probably me and the way I am using it.
Is this better than I had a couple of years ago? I am not sure. Seems different at least.
It is a question many devs miss. what happens when I put this in the wild and I now have hundreds of them.
In this case it is probably scanning aggressively. Just incase you plugged in a new devices in the past 100ms. Then some sort of filter with data compression (hopefully) and then sending its exfiltrated data back home. Honestly, not a cool thing to do and makes your customers NOT trust you. I had an old LG TV that was doing this 15 years ago where it would send every button press back to LG. I unplugged it. It agressivly scan its empty socket.
That seems to be a very broad statement. For example in a system where interrupts mostly control things this sort of 'do not close the program' could be useful.
A guy I worked with had one I never would think of because I do not work in that field.
But yeah a warning would probably be useful.
The reason I joined FB no longer exists for me. I remember why I stopped talking to many of the 'friends' I had. I silenced all of them and only join interesting groups now. Even then I only log in once or twice a year.
Now you could pull particular items out of their grid. Just need the wires and panels to make sense. They would not care about that either. It is only if the panels are plugged into the grid they start to care. Downside is sometimes waiting for that battery to have enough juice to work. It goes faster than you think and some battery systems are decently expensive just by themselves, on top of the panels/inverters/controllers/install.