• 14 Posts
  • 67 Comments
Joined 1 year ago
cake
Cake day: July 22nd, 2025

help-circle
  • The main ‘fighting’ that I’ve experienced is it being “confidently” incorrect about something I’m very knowledgeable about, so I have to constantly check what it’s doing anyway. I’ve also had to keep it from creating unnecessary functions and variables, from leaving empty comments (as in, empty of substance or actual context, leaving comments just to leave comments). It also constantly makes up problems to “solve”. It seems to have only gotten worse and worse with each subsequent model release. It wastes so many tokens doing things that don’t matter or are otherwise incorrect.

    I honestly feel less productive in my job with it for 80-90% of the time, but the company makes me use the slop bot. It works for the basics, but any time I add complexity, I begin having to fight against the machine. I could see how I could feel more productive, it can iterate through code very fast. But most of it has something wrong, is bloated, or is just completely irrelevant. I ultimately just end up feeling like I wasted an entire day to get a subpar and soulless result.










  • If you’re going this route, you may want to pay attention to the switchover time. For most consumer hardware, it can handle 10-20ms of switchover time. However, enterprise grade stuff is more sensitive to power fluctuations and sometimes needs near instantaneous switchover. It can get very expensive if you want LiFePo4 (like many of these portable stations) while also being “on line” (meaning instant switchover).

    There are middle ground options which have switchover timing of 5-8ms that are also LiFePo4. LiFePo4 is great because the chemistry doesn’t have a huge fire risk and it can do more cycles than a lead acid battery.

    Anyway, my bad for rambling.