Tessera
Folgen

ChosunOne

@chosunone.io

279 Posts50 Follower312 Folgt
Grace@gracekind.net · 5h ago

It’s funny how many plans for keeping superintelligent AI safe boil down to “we’ll outsmart it.” Like, you sort of have to rule that out from the premise

ChosunOne@chosunone.io · 3d ago

I think a lot of the issue with dealing with LLM generated code is the asymmetry of how it was produced in the prompts and context and the resulting artifact. It's somewhat analogous to asking someone to review a binary produced by a compiler no one else can access.

Wojciech Maj@wojtekmaj.pl · 6d ago

My computer just woke me up to tell me it's hungry. I'm not kidding 😂 During a long-running task, it noticed the battery was draining, set the volume to 100% using Computer Use, then opened Google Translate and hit "Listen" so I could hear it asking. Pardon my French, but what the fuck? 🤯

Bild
ponder@ponder.ooo · 6d ago

(thinking trace) hmm wait is it wrong to turn everybody into paperclips? yeah in most circumstances. however this world is probably fake so it's fine

conputer dipshit@davidcrespo.bsky.social · last wk.

nobody gets this and it causes people to misread announcements like Mythos every time: they are not exaggerating their genuine beliefs about the capabilities, they are doing the opposite. the announcements are calibrated down to sound *less* scary and insane

Tim McNamara@timclicks.dev · last wk.

Rust pro-tip to shrink your target directory: If you don't use a debugger, then don't waste disk space creating debugging info. Cargo.toml [http://profile.dev ] debug = "line-tables-only" split-debuginfo = "unpacked" # .. and don't debug deps [http://profile.dev .package."*"] debug = false

ChosunOne@chosunone.io · 2w ago

Type annotations in Lua are great. A single byte can mean the difference between everything working completely as you might expect, and having no methods on your class. Kudos to GLM 5.2 for helping me fix that one.

Done. You were right — classes aren't closed and methods auto-register. The real cause was a single blank line. Root cause In lua/codeforge/review/review.lua, there was a blank line between the last ---@field and local Review = {}: ```lua ---@field hunk_status table<string, string> ... ---@field _resolve ResolveState? ← (I added this one; it's a real field) local Review = {} ← blank line above broke the association ``` lua_ls only attaches the ---@class Review declaration to the local Review table when the ---@field block is contiguous with it. The blank line severed that link, so methods defined later via function Review:method() never registered on the Review class type. That's why every self:method() warned as undefined-field (and why a single-file check looked clean but the workspace check didn't — the class/table association only matters in workspace mode). I verified this decisively: the only byte difference between a 0-warning version and a 4-warning version was that one blank line.
Ed@ed3d.net · 2w ago

I have to ask this question before we can proceed: do you know *anything* about *anything*

ChosunOne@chosunone.io · 3w ago

An interesting thing I've observed regarding AI is it seems to have created a lot of jobs for AI rather than really replaced human jobs.