M0r13n

> often preferring downstream fixes/hacks/workarounds when upstream fixes would be better.

It sometimes feels like the model is too lazy to do the actual reasonable fix and implements a _hacky_ fix downstream. And to be honest: I feel that!

This weekend I had some time with Opus 5.5 and GLM 5.3. I went over some findings in a library of Claude Mythos 5.1. These were minor, low-severity bug fixes and Mythos provided a PR to address them. Its PR was functionally correct. I still spent ~5 hours looping over them until I was really happy, even though a fully working PR already existed.

Some of the differences were:

- Mythos recommended salvaging damaged labels. I pushed back: data whose structure is broken shouldn’t be trusted

- My simpler more readable test caught a regression that Mythos’s more elaborate test missed

- Mythos allowed invalid values, citing real-world data that I could not reproduce, while I decided to follow the spec

- Mythos kept the old error types. I made every kind of malformed input raise the same error, and accepted a small, documented breaking change for anyone who relied on the old ones

Overall, I much preferred the final version of my PR to the initial draft Mythos provided. However, getting there involved quite a bit of time messing around with the code, as well as some back and forth with Opus (which was valuable).

This is a recent example that matches my overall experience working with current SOTA models (the ones mere mortals like me have access to).

TL;DR: I don’t think AI already has better judgment than (most) senior people. Obviously, that might change with future models. But that’s a hypothetical scenario. It might as well not change anytime soon.

Ask ChatGPT:

> Generate a realistic image of a bad fitting suit without looking obviously fake

Create a new chat and attach the image generated previously:

> Please rate my suit

You will receive an answer that reads something like this:

>7.5/10 — clean, professional, and well coordinated.

Yeah, I don't think superintelligence is imminent.

This seems to assume more code shipped equals more work done. I am still not convinced that this is necessarily the case. Sometimes it is. Sometimes it is not. You mentioned that reviews are now the bottleneck and that your familiarity with the code has decreased. That tradeoff might eat into the parallelization gains over time.

Exactly. I follow a similar workflow. I am still writing code by hand. Not all code. Parts are generated by Opus.

> look at my postprandial response to dosing for the past week and make ratio suggestions for breakfast, lunch, and dinner

I'm not so sure about that. A patient absolutely must critically evaluate the LLM's suggestions. A naive user risks severe complications. A user with that kind of competence, however, doesn't need an LLM for such trivial adjustments - they're obvious

> But for kids or the elderly, I see a use case.

These are exactly the kinds of people who should NOT base their diabetes management on the "suggestions" of LLMs! There is the real risk that such users lack the competence or judgement to critically assess the convincing-sounding output of an LLM.

I don't think that LLMs are trustworthy companions in managing a complex metabolic disease like diabetes - especially if you deviate (ever so slightly) from the norm (very lean, very active, strict diet, etc.)!

I'm a T1D myself and like to experiment with ChatGPT (or Opus). My experiences are mixed

LLMs are overly cautious when it comes to correcting with insulin. They regularly advise against correcting before going to bed, even if this means that my blood glucose remains above 140 mg/dl for the whole night.

I am following a low to medium carb diet (<100g a day). ChatGPT always nudges me to consume more carbohydrates, even though I have a TIR of 90% (70-150 mg/dl). Why would I change my diet if it currently works very well for me? Still, most LLMs seem to favor carbs for some reason.

I am using Fiasp as my fast acting insulin. Typically, I inject around 1 to 4 IUs of Fiasp. Its glucose-lowering effect typically lasts for roughly 2-3 hours. Therefore, I know that it is safe to re-inject after three hours without risking insulin stacking. But ChatGPT regularly advises against that and wants me to wait another 1-2 hours.

I am not against automating diabetes management. In fact, I really appreciate projects that help with that. But I don't consider LLMs to be helpful in this regard. Their combination of training data bias, liability aversion, lack of context, and one-size-fits-all thinking disqualifies them from such tasks.

> Also your in winter are you running the heater constantly?

Nope. But last winter it got really cold (< -10°C). Also the Honda was aggressively heating the battery

I agree. Though I replaced it with a car with a capacity of 40 kW and better overall efficiency. You're right, however, that I could have bought a used VW ID.3 or similar. But I can't stand how these cars look or feel. I'm also not complaining. I really like my car. I just wanted to share my experience :)

yes!

Sadly, I don't own a wall box. So I'm dependent on public infrastructure. If I could charge at home I'd be even happier with my car.

It depends where you are. I live in a somewhat rural area in Northern Germany. There are some chargers, but many of them are out of service like the one next door. I've never stumbled upon a free charger though.

I've had a rough time with the last two EVs I've owned. I bought a Honda e in 2020 because of its retro-future charm, but ended up being disappointed by several things:

- the range was miserable

- the software quality was bad

- no OTA updates ever (despite Honda's promises)

- slow charging

- poor public charging infrastructure in Germany

I should have known that a 35 kW battery wouldn't deliver great range or charging speed. But I didn't fully appreciate how limiting it would be.

Last year, I bought a new Mini Cooper e. Larger battery. Better software. BMW's quality actually delivered this time. The car feels objectively nice. The software is polished. There are updates. Few bugs. But the range still leaves something to be desired. In summer it's okay. During winter 30-40% of the range just melts away.

Public charging in Northern Germany still sucks:

- too few public chargers

- chargers are often broken or out of service

- pricing is intransparent

Municipal utility companies ("Stadtwerke") seem especially bad at maintaining their charger fleets. Every second charger that I want to use is out of service. The one next to my apartment has been labeled as "defective" for a couple of weeks now. Nobody seems to care...

I still like (love during summer) my car. It's a cool car. It feels luxurious. It's comfortable. It's fun to tear around corners. It's still compact enough to maneuver through the city. And it looks cool. But it also costs 40-50k EUR and only has limited range. And public charging really needs to improve.

My comment was not intended to be any criticism or to downplay the performance - quite the opposite :)

JFrogs platform is fairly robust. Only time will tell if this project can keep up. I highly doubt it's more than a fancy-looking prototype at this stage

Thanks for clearing that up! :)

A few weeks ago I noticed DNS4EU couldn’t resolve archive.is and assumed it was just a configuration mistake. I emailed them about it, and after a couple of days or weeks (not really sure) the domain started resolving again. Given AdGuard’s recent report about suspicious pressure on DNS providers to block Archive.today, I’m starting to wonder if DNS4EU’s temporary block was actually related to the same campaign

Personally, I have never liked the PEP 634 pattern matching. I write a lot of code in Python. 99% of the time when I could use pattern matching, I am going to use simple if statements or dictionaries. Most of the time, they are more straightforward and easier to read, especially for developers who are more familiar with traditional control flow.

I am running an ARM64 build of Ubuntu on my MacBook Air using Multipass. I've never had a problem due to missing support/optimisation for ARM - at least I didn't notice any. I even noticed that build times were faster on this virtualised machine than they were natively on my previous Tuxedo laptop which had an Intel i7 that was a couple of years old. Although, I blame this speed mostly on the sheer horsepower of the newest Apple chips

I can absolutely relate to this. I had similar feelings for the last year or so - although I couldn't express these thoughts as well as the author did.

I've developed this weird addiction to making notes in Obsidian. It wasn't really about learning or understanding anything. I bought into the illusion that having notes in my PKM meant I had actual knowledge. Bigger graph = smarter me, or so I thought. I even started reading books just to feed the system: Look at me with my 3,587 notes this year - aren't I clever!"

Currently, I am just taking notes where it really matters: Readme, documentation and some loosely organised markdown files

I am confused, because this means that you won't be able to install anything. No compiler, no 3rd party libraries and no text editor that isn't preinstalled

You're right. But they explicitly wrote "we examined the potential of FUS as a treatment for diabetes". So they are discussing a treatment, not just symptom relief

> But in people with diabetes, this sensing system is dysfunctional, and the liver releases glucose even when blood levels are already high, causing a host of health problems.

I am pretty sure, that the dysfunctional glucose sensing and inappropriate liver glucose release are consequences and complications of diabetes, not the primary causes. Diabetes (Type 2) is primarily caused by insulin resistance combined with progressive beta cell dysfunction.

Therefore, treating the liver to treat diabetes seems .... weird?

It is shown under the search box right before the first result

I am a proud user of their assistent. It provides access to all models that I am interested in (basically only Sonnet/Opus) with stronger privacy guarantees than many of their competitors. Their UI/UX has definitely room for improvement. However, I find it pretty useful.

It has. But in my experience their own index is rarely used

> All results from external indexes.

The above is something I see all the time when using Kagi.

Thank you!

I never heard about the supplementation of N-acetyl-cysteine with regards to the treatment of dry eye disease (DED). Could you elaborate on your experiences with the supplementation of NAD? I am unable to find any real useful information in the web