I actually convert the SDFs to voxels and render triangles, but.. some people have written direct SDF renderers. There's a guy that posted to YouTube not too long ago that wrote a really cool one with physics and everything
The weird thing is I've seen LLMs "typo" stuff pretty often. Yesterday I asked Gemini a question about the Python Twisted framework and it answered about Deferreds but misspelled it as "Deferends" in one spot.
Pi * r2 (squared) both pans. Divide smaller pan area by larger pan, now you have the % of how much the smaller pan recipe fills up the larger pan, and the missing % you need to fill. Increase ingredients by that % divided by the filled %.
Small pan area: 20 sq cm
Larger pan: 48 sq cm
20 / 48 = .42, I'm missing .58 of the pan. .58 / .42 is 1.38. My recipe needs 2.38x the original to fill the larger pie pan.
Having used Claude a lot for the past four months, I get exhausted from its style. Every sentence has been buffed and polished and enhanced and it never just plainly says a thing. It's as if you have to eat every meal with every possible flavor enhancer in existence. At one point I will totally lose it if it mentions "smoke test" one more time.
It is also totally not what I want for docstrings in code or Powerpoint drafts, where consistency in language is critical.
Like I said in another thread, everything Claude (Code) writes sounds like it’s congratulating itself of how smart it is. While not actually being that smart.
I believe AI technical prose peaked with Opus 4.6. I still use it (mostly for that purpose) and I think it's legitimately great. I'm hoping they are able to reverse the trends that benchmaxxing and RLAIF have wrought on Claude's non-code output with the future models.
Now that the public anger is growing i really hope Anthropics next models seriously address this. Or for that matter, i hope everyone (OpenAI/etc) starts focusing on this too.
Intelligence is important but it feels as if the LLM is only capable of conveying information while drenching it in vomit.
Claude Code's creative use of language in an engineering context is often quite infuriating. I want language to be as simple as possible, it should be accessible and require as little context as possible. Below are a few examples that Code wrote that I encountered in my own work (related to signal processing):
"excursion"
(means: a spike/jump — a value that rises or deviates from baseline, just say spike or outlier)
"legitimate majority-normal baseline"
(means: a real majority of normal pixels)
"matched pool of pure-noise ('normal') pixels"
(means: the same number of normal pixels, don't bring pools into this)
"ablation"
(means: comparing before vs. after — turning a thing on/off to see what changes)
I actually used Claude Code to try and find examples like these but not entirely unexpectedly it had a very hard time detecting these, even though I encounter them like every other sentence. I can imagine this style is great when writing prose, not so much when writing documentation.
Similarly, I tried using Claude Design to make some slides, and the individual slides were fine, but just about every other slide it used different words to denote the same concept, which I would say is the fastest way to lose your audience.
I've always used em-dash. I got familiar with the hotkeys when I started using Mac OS X in 2002. Option+Hyphen for en-dash, Option+Shift+Hyphen for em-dash. It's unfortunate that it's an LLM tell. I'm glad the LLMs haven't subsumed proper ellipses yet…
It is. They are also enshittifying Komoot and EventBrite. Also by default they acquire a company and fire all staff within the week. Fuck Bending Spoons.
Pre-bending spoons Komoot was a beautiful app and community.
You could operate it one handed with your brightness turned all the way down and easily get the info you needed.
Now when I pull it up mid ride to route home I have to click through multiple upgrade to premium pop ups with tiny exit crosses.
All good things etc etc
Founders decide they want to do other things with their lives all the time, and in the case of komoot reportedly exited at a €300m valuation for a company that had raised very little VC money, which is going to tempt most people no matter how much they hate popups...
is firing staff after acquisition inherently bad if it's the same staff/management that led to the app being devalued and losing users in the first place though
Labels literally negotiated their own royalty rates down in exchange for shares in Spotify. It’s the perfect way to push artists out of receiving earnings.
I think record labels would be first in line to buy Spotify if it was ever for sale.
Why do you think that a platform with so many customers as to be industry defining, with dozens of interface options, with a massive feature set, with a global footprint and basically flawless uptime requirements, could be kept running by two guys?
reply