@jalefkowit [looking at the results] ah for fuck's sake

@jalefkowit must be something in the air

In other words:

```
def func(a, b=2, c=3) {
// ...
}

func(1, c=42) // equivalent to func(1, 42, 3)
```

The fact that #Groovy allows you to spell out a call that *look* like you're passing parameters by name, but they're actually passed by position and the "names" are ignored

is criminal

@glyph I give it slightly better than coin-flip odds that I'd know if I hadn't studied accelerators before I came to software professionally, and only slightly better because the Well There's Your Problem podcast did an episode on it and I probably would have found them anyway.

@glyph may mercy smile on us reading too much into the initial response

@glyph [votes, looks at initial responses] oh no

@aud the value of "I don't know" is wildly underappreciated even when the atoms of a system are human beings (cf. programmers/other SMEs almost never say these words) so it is depressingly understandable that ML as a whole is not very interested in it aside from parlor tricks

@aud this is the only reason I work in the industry at all, $employer's secret sauce classifier has explicit support for uncertainty.

As in, not faking it by thresholding a softmax and pretending all-below-threshold is an N+1th class. It's pretty rad, actually.

@aud the really frustrating thing is that in this case, I *can* reliably say that the ticket will take a day or two. It's mostly deleting code.

I just don't *want* to fall into a loop where the PM comments on every single ticket filed asking "how many days????" and I know that every time I take that unserious question seriously, I'm setting a precedent.

Me: [filing a ticket for at least three months from now]

PM: how many days will that take?

It took a solid 3 hours and reverse engineering the answer without the help of the authors of the upstream changes, but I finally understand the scope.

It doesn't have to be like this but boy does it seem to happen a lot :blobfox0_0:

@molly0xfff ahh, memories…

Well, I'm angry about this again. Some amount of shouting was involved this morning after I dared to try and be sure we actually understand what feature we're supposed to be implementing.

Having cooled down a bit, I own more of this problem than I was initially giving credit for.

HOWEVER, the reason I own that part of the problem is because of previous hacks shoved in because of similar "yea whatever just slap something together and don't ever specify the data/behavior" reasons

It's just an exhausting way to develop software that is meant to be reliable for more than 2 weeks.

I'm so sick of this mickey mouse crap. Move slow and break as many things as possible, I guess.

OH LOOK it is a critical feature for the release being specified AFTER the release

AGAIN.

@skinnylatte it truly is the official car of dumb guys

@skinnylatte I miss her too, even only knowing her through the screen 🫂

@jalefkowit also positively REELING that some of the images in the guide are photos of a monitor, but *only* some