niccl

In some book by P G Wodehouse (inventor of Jeeves the butler), one character says (out of nowhere) that all the humans on the planet could fit in a cubic hole 1/2 mile on each side. It took me a little while to convince myself that was true. It still is, apparently

and the luxury to laugh when it's completely off the rails

I'd love to see some sort of histogram of different styles of AI usage for coding: how many people just use Chat v Claude v something fancy that I don't know about v something even fancier that I don't know about v ...

And if there were a dimension of day-job v personal use, I'd be even happier

Does anyone know if such a thing exists

There is a problem with the over-under method use for long cables. If you then grab the wrong end through the centre hole you end up with a cable with a bunch of overhand knots in, which I find much more tedious to deal with than just using normal looping of cables and making sure to add the twist each time.

Back many years when I was touring with bands, at the end of the night you'd see all the lighting crew walking around the stage coiling the long cables, with one end trailing after them, to make sure the twists were correct. That was much more useful than generic over-under for all cables.

over-under has its place, but I don't use it everywhere.

any specifics on what you did?

I find them almost unintelligible. I'm a native English speaker. I read a lot, so I think my comprehension should be at least OK. I'm not even particularly stupid. Yet when faced with things like below (a direct copy/paste from a handoff document in a long running vibe-coding session), I have no real idea of what it's trying to tell me. Is it important? Do I need to do anything?

I think that spending all day trying to parse stuff like this is why a long session is so exhausting

> Worth stating because four documents now assert it. The console freeze was recorded in exactly one place with exactly one justification — a dead drag handle during a booked half-day you do not get back — and handoff-4.3-done.html's own wording is that 4.4's review page "could not break the console, but the downside of being wrong is that half day". No second reason. Checked, not recalled.

This recalls a time I was driving the Desert Road in Aotearoa/NZ at dawn. As I got to the top of the hill the sun came up in line with all the power lines and they glowed like golden spider webs off into the distance. I'd never thought that power lines could ever be breathtakingly lovely. This was one time they managed it

nit pick: _So Long_ and thanks for all the fish

I'm really sorry about that, but it jarred my ASD-ness

They mention 'breaking rapport' a few times. I'd really appreciate if someone could explain to an ASD person what that looks like. Genuine question

IIRC, at one time, in Aotearoa/New Zealand at least, Coca Cola Amatil (or whoever it is) had trademarked 'Always'. It may have been some other word, but it was definitely a common word. And it wasn't the particular branding, just the word

It seems that management in most organisations can't believe something unless they've paid vast sums for it. So they can't believe their own staff if they say X, even if it's right, because they haven't paid enough for it. Then the consultant comes along, interviews the staff, finds they say X, tell the client, charge buckets for it, and are believed. Weird human behaviour...

disclaimer: ex management consultant

> For instance, Shakespeare’s characters call one another “cuz,”

Calling someone 'cuz' is quite common in Aotearoa/NZ.

No. I got from the article that he's saying that the purchase is sunk cost, so any sale is 100% profit. So it's correct