I have heard "the poor type safety" argument from writers of strongly typed languages for many many years. Having written js and python for a large amount of my carrier I can count on one hand the number of times I've found a bug that was due to a type issue. With LLMs it has been the same pattern. They don't seem to produce issues with types.
The feeling of being an outsider because you don't know the acronym is just as real in non-public settings. The new guy on the team for example. There's a real feeling that you should already know it, even if it's the first time you've heard the other person say it. The first time you heard GBIF, did you know what it meant? How did you feel when you heard it?
There's really a feeling now pushing back against learning in general. The feeling is that it is pointless since technology would just do it for you. When I started learning Chinese a friend just wouldn't stop talking about how the latest airpods will just be able to translate for you. It was really rather demoralising. But there is still something incredibly rewarding about having that knowledge in your own head and not having to go find someone or something to ask. I push on regardless.
It's about not understanding someone because you haven't been in their shoes. Even if they don't understand themselves, it doesn't make the way they feel about their own past somehow invalid.
They will never be able to actually have human experience. I think that's the point. It's not that they won't be able to pretend that they have had human experience, it is that they just haven't and cannot ever do it. It is never futile to do what a computer (or even another human) can do better than you, because your experience does matter.
Until you have to deal with bed and breakfast rules for RSUs. Good luck getting free software to understand that. There are a couple of open source attempts but they are skeleton at best.
At certain times of day the London underground deliberately directs people to longer paths around the stations to alleviate congestion. This kind of thing could be a health benefit.
There's an industry wide deficit of tests for AI right now. It's not just this tool, it's everything you add to your code base or your development flow that uses AI. Nobody had tests for "how fast/well was this developed" before AI and they haven't added them now.
Right but they also state they have never implemented TURN which IMO is a marker of WebRTC expertness. (I haven't btw, just the WebRTC experts I know absolutely have written or worked on at some point a TURN implementation)
I've been struggling with markdown recently as I really want the claims it makes in documents to be programmatically verifiable e.g. citations, I want a simple script to check that each of the files and lines of code it references actually exist. Perhaps HTML can be used for this. It certainly has a better chance than markdown.
Surely there's a googler on here who actually knows whether they are doing this. Anyone actually know or is this post all about Chrome bashing and speculation?
I think it's a reasonable statue. But does anyone else think it's a bit obvious, more so than his other work? Like there is no doubt on the meaning at all, it's all right there on the surface level.