• 1 Post
  • 13 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle





  • One thing I’ve also noticed is people doing code reviews using ai to pad their stats or think they are helping out. At best it’s stating the obvious, wasting resources to point out what doesn’t need pointing out. At worst it’s a giant waste of time based on total bullshit the ai made up.

    I kinda understand why people would think LLMs are able to generate and evaluate code. Because they throw simple example problems at them and they solve them without much issue. Sometimes they make obvious mistakes, but these are easily corrected. This makes people think LLMs are basically able to code, if it can solve even some harder example problems, surely they are at least as good as beginner programmers right? No, wrong actually. The reason the LLM can solve the example problem, is because that example (or a variation) was contained within its training data. It knows the answer not by deduction or by reason, it knows the answer by memorization. Once you start actually programming in the real world, it’s nothing like the examples. You need to account for an existing code base, with existing rules, standards and limitations. You need to evaluate which solution out of your toolbox to apply. Need to consider the big picture as well as small details. You need to think of the next guy working with the code, because more often than not, that next guy is you. LLMs crumble in a situation like this, they don’t know about all the unspoken things, they haven’t trained on the code base you are working with.

    There’s a book I’m fond of called Patterns of Enterprise Application Architecture by Martin Fowler. I always used to joke it contained the answer to any problem a software engineer ever comes across. The only trick is to choose the correct answer. LLMs are like this, they have all these patterns memorized and choose which answer best fits the question. But it doesn’t understand why, what the upsides and downsides are for your specific situation. What the implications of the selected answer are going forward. Or why this pattern over another. When the LLM answers you can often prompt it to produce an answer with a completely different pattern applied. In my opinion it’s barely more useful than the book and in many ways much worse.



  • Nope these ones did it from the get go. We asked about it when they got installed, it was a feature to let you know they were operating properly. I really to this day don’t know why it was like that.

    It wasn’t a loud beep, when the TV was on, you couldn’t even hear it. I only heard it when it was quiet in the house, especially when I wanted to sleep.


  • We used to have a fancy ass fire alarm system in the 90s and early 2000s. At a couple of points in the house there were detectors, each with a battery, power connected and connected to each other. If one of them detected smoke or heat, they would all start beeping. They would flash every 10 secs to let you know it is in sync, but they would also emit a small beep every 10 mins or so. They never ran out of power since they were connected to mains voltage with a battery backup. The battery was rated to be replaced every 10 years, but I think it was one of those that basically went on forever.

    I got used to it after a while, but every now and again I would start noticing the beeps and could not stop noticing them. My dad was proud of them, he paid a lot of money to get them and get them installed.





  • That’s because of the way these scales work. They use a material that deforms under stress and when it deforms the resistance changes. By putting current through this material and measuring the voltage drop, it can be mapped to how much stress the material is under and thus how much weight is on the scale.

    This is a pretty roundabout way and has a lot of caveats, but it is very cheap. So cheap scales always work this way. That’s why they aren’t super accurate and have deviations depending on things like temperature. Another big downside is any permanent deformation ruins the calibration, giving incorrect results. That’s why you never put more weight on kitchen scales than it says, it will break them.

    The issue you are running into is the way it measures. It applies a very specific voltage and current in order to get the result. The lookup table it uses is only valid within a narrow range. When the battery voltage goes outside that range, it can no longer perform the measurement. Even though there’s plenty of juice for things like the little processing chip and the LCD display. They don’t need a lot of power and can do with low voltages. But it can no longer weigh anything so it just errors out with a low battery warning.