Literate programming as an ideal works at very very high level and very very low level. Plumbing code often doesn’t benefit from comments at all, and is the usually the most subject to refactoring. Code by amateurs/neophytes is often not gonna be written in such a way that a clear description of the intention or mechanics is achievable by the coder. Unobtainable standard, smh. I like comments with a ‘why’ at the top and a ‘what’ at the bottom (of the stack. I’m talking about abstraction layers. Why am I doing this piece of logic in the code you can clearly understand at the top, what the fuck am I doing these weird shenanigans with a fucking red-black tree of all things in this low level generic function)

Sometimes you just need to document the business reason behind what you’re doing, regardless of how clear the code might be 😆

For a month or two I still kept the app on my phone. As a memento.

Reddit’s official UX experiences suck balls

Some of them, sometimes. But some are adulated and free and contribute vast swathes to our culture and understanding.

I, too, know people in Oxford, however none of them are insane, so none of them have described it that way 😅. If you’re sold on AI as well then, yeah, lol, I guess that tracks. Wanna buy some NFTs, bro? 🤣🤣

Wow, hot take. Do you know what a traffic filter is? It’s just a restriction on through traffic, so that smaller roads aren’t used as part of a route by people going longer distances. It in no way restricts the overall distance that people can travel. In fact it’s less restrictive than some LTN implementations, since at least the road can still be traversed

Where do you think this has been implemented? I’m curious, because you’re the first person I’ve come across who was this take, and it’s novel to me.

For the ‘I use … BTW’ meme to say something else.

No, actually, I can’t think of anything. I’m pretty comfortable with it at this point. Been running it since 2013…

This is the most excellent summary of Go I have ever read. I agree with everything you’ve said, although as a fan of Scala and in particular its asynchronous programming ecosystem (cats for me, but I’ll forgive those who prefer the walled garden of zio) I would also add that, whilst its async model with go routines is generally pretty easy to use, it can shit the bed on some highly-concurrent workloads and fail to schedule stuff in time that it really should’ve, and because it’s such a mother-knows-best language there’s fuck all you can do to give higher priority to the threads that you happen to know need more TLC

As more and more libraries are open source on GitHub or gitlab or sourceforge or whateverthefuck, asking questions on the libraries themselves (as an issue) is often the right thing to do, too… Less centralised than SO but also the only people who care about how to do things in a lib are people using the lib, so…

Wellllll the implications of the ending of 28 weeks later is that the rest of the world had a reprieve but are fucked eventually…

Is that true about the debug build? I had it on the N64 way back when and don’t remember it being especially laggy. OTOH I was young, and relatively shit at computer games

I never saw such a potent combination of gender politics and prolog