Hacker Newsnew | past | comments | ask | show | jobs | submit | watt's commentslogin

I'll posit that the distinction does not matter: the whole Chinese Room line of discourse has been counterproductive to putting in actual work.


Very poor audio quality, not listenable. Why do folks insist screaming into microphone and overloading the recording where it just nasty clipping?


Also not sure what microphone was used but a pop filter would have helped.


It sounds like some dynamic gain is happening every time he starts talking, and then after ~1 second it gets better. I don't think it's a "missing hardware" issue, just turning down the gain would probably be enough, or tuning the software dynamics if he's using that. Could also be that the podcaster tried doing some normalization across the entire podcast while mastering and fucked it up that way.


It's cute when somebody very smart pretends to be "grug brain" but loses it's appeal when somebody pretty obviously not smart at all is exposed for what they are.


Crack on with it and don't keep us in the dark!


sufficiently advanced troll becomes indistinguishable from the real thing. think about this as you gaze into the abyss.


If think the attention is in proportion, people are reacting just like when a body has an inflammation. If a person of _this_ calibre can be fired, and not even fired, disposed as a used-up tissue, it is a sign of times.


I find the comments Copilot proposes is better than average comment quality for the code base I routinely work on: maybe you are so great you don't need any help ever, but that's not true for the average software dev.


> I find the comments Copilot proposes is better than average comment quality for the code base I routinely work on

Maybe the average is just so bad? The completions I get for comments are document what the code is doing, which is not something that I ever put into comments. It's always:

a) A highlevel (prefixed to the function/block/scope definition) list of steps, input expectations and output expectations for the forthcoming function/block/scope

Or

b) A note explaining why the code does what it does.

A comment repeating the code but in English is useless.


The best comments are the type of:

  Whatever bad thing you think of this part is probably true, but I can’t do better.
And

  Beware, weird optimization ahead.
And

  Editing this code requires arcane knowledge.


It's not that my comments are infallible, but if I write something wrong/silly it'll be caught during code review. similarly if there's a comment missing before some arcane nonsense nobody will remember in 3 years, then i'd expect a PR reviewer to tell the dev to add one.

Copilot just likes to puke very useless comments whenever I type "//", especially in autocomplete mode (I don't really use the chat mode).


well, C# and TypeScript is thanks to Anders Hejlsberg who does have sense of style.


I hope they can do some reinforcement learning from Stack Overflow moderator decisions also


(2018). So it's 7 years later, nothing has changed. Same old.


Arguably it's gotten even worse. LLMs are the next order of magnitude of software inefficiency. And they're gonna copy all the same patterns that got us here.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: