Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AI;DR (AI; Didn't Read)

rickmanelius.com

Post reply on HN
Print view View original

481–490 of 729 posts

Re: AI;DR (AI; Didn't Read)

#481

Post by supermatt »

voxelghost wrote: post #479
supermatt wrote: post #162

Earlier quoted context omitted.

How is this? https://claude.ai/share/99bfee0f-bab9-4593-aabb-377e71f1151d

I asked claude 4.5 : """ Please, with an absolute minimum of content modification, edit this text with proper paragraph-formatting, spelling, punctuation and grammar. Do not alter vocabulary, language, or tone. """ And then fed it your input. And the output was a very easily readable, enjoyable plain-ascii-text, with no Ai-ick, except for an em-dash or two. Tried pasting it here, but that removed paragraph formatting

Thank you. Someone else posted similar with ChatGPT and it looks like that strategy could be a way for me to manually edit a lot more easily.

Re: AI;DR (AI; Didn't Read)

#482

Post by johnnyanmac »

dragontamer wrote: post #439
stronglikedan wrote: post #248

Earlier quoted context omitted.

Doesn't matter. You'll come off as the baddie. It's the foreseeable future. Best just to learn how to interpret AI generated shit, or learn how to run it through AI and have it translate it to a more concise format without all the buzzwords. It'll take getting used to, but it'll save your career.

Bring it up in a bar or otherwise off work. There's a reason 3rd places exists. There's a social construct that off-work discussion (even when on-work) stays off work. If your coworker is professional and cares about keeping channels open, they too will respect the unspoken rules that govern 3rd place neutral locations. Blame it on the alcohol later on if it actually pisses someone off.

>There's a reason 3rd places exists.

Not anymore these days.

Re: AI;DR (AI; Didn't Read)

#483

Post by m12k »

Throwing unread AI output at others is the new version of “sitting on your phone, oblivious to those spending time with you”. Every new consumer technology comes with a new way of being rude.

Re: AI;DR (AI; Didn't Read)

#484

Post by ulrikrasmussen »

akomtu wrote: post #448
ulrikrasmussen wrote: post #442

Earlier quoted context omitted.

What is this defeatist attitude? I don't know where you work, but it is not my impression that AI has instantly turned all developers into mindless AI-pilled sheep. If you feel like a simple suggestion like that will cost you your career, then it doesn't sound like a place where any constructive criticism would have been accepted even before AI.

AI is more or less a religion right now in the corporate world. Speaking against AI amounts to heresy.

There is no single conforming "corporate world" that applies to all companies. If AI is treated religion in your company that sounds like a local problem, even if it seems like a trend.

Besides, GP was not talking about corporate, but about the inability to even suggest an improved usage of LLMs among their developer peers, as if every line of code generated by AI is now gospel and questioning it is treated as heresy. This level of defeatism is beyond cynical and approaching childish.

Re: AI;DR (AI; Didn't Read)

#485

Post by kristjansson »

eru wrote: post #457
kristjansson wrote: post #417

Earlier quoted context omitted.

And the tests. Oh god the tests. Personal recent favorite: I asked for some changes to a Dockerfile, which it did ably, and then promptly tested by writing a pytest module that traversed up to the root, read the Dockerfile, and checked that the added lines were present.

Try property based testing perhaps.

I'm generally happy with the tests I ask it for, some of which are PBT. It's just the insistence upon memorializing every single change with a test. Maybe encouraging / forcing PBT will dissuade it?

Re: AI;DR (AI; Didn't Read)

#486

Post by atomicnumber3 »

noman-land wrote: post #113
LPisGood wrote: post #56

My coworkers continue to dump hundreds of lines of AI documentation in every PR and every other line of code has between one and ten lines of AI generated comments, talking about the real unlock and how things are byte for byte identical on the load bearing path or how the acceptance ladder is misleading. Features are coming out and metrics are improving, but we’re basically in a post readability code base, with the…

Have you considered talking about it? You're in a professional environment collectively working in a new way with a group of people. It's up to somebody to have opinions about what does and doesn't suck. If you silently go along and don't say anything you're dooming yourself and all of us to a lifetime of this garbage.

No, if he speaks against it he gets labeled "anti-AI" and laid off or not promoted. If he stays silent he retains his job.

Corporate Capitalism's main innovation was virtualizing feudalism. Now anyone with a bit of cash flow can be a feudal lord with peasants to do his will. No need to maintain land or fight over it with other feudal lords. There's still fighting, naturally, but now the game isn't zero sum.

The serfs don't get any real say in this model. At best you can bend the lord's ear if you're sufficiently trusted an advisor. But part of the reason you're trusted is to be trusted not to treat the lord like he's too much of an idiot.

A huge problem is that capitalism rewards cash flows and accumulated capital so powerfully that lots of other things just don't matter, potentially for a very long time. Look at GitHub. This leads to immensely extended fuck around phases and "find out" looks like IBM (fossilization and bizarre holdings corporation / dead company parking lot) just as often as it looks like Enron.

Re: AI;DR (AI; Didn't Read)

#487

Post by johnnyanmac »

ninkendo wrote: post #389
rbongers wrote: post #309

Earlier quoted context omitted.

Two very useful directives to give AI when it comes to documentation: 1) Document what's there, not the diff. Documentation of how code was removed or changed to fix a bug or add a feature is not useful and difficult to maintain; documentation should explain how code works now. 2) Documentation should live close to the source as possible. Prefer line based comments and standardized function documentation. Top-level s…

> Document what's there, not the diff We recently added a similar thing to our style guide, It’s astonishing to me that we have to spell this out, that something as obvious as this needs to be explained to LLM’s at all. They’re supposed to be exceeding human intelligence, at least at things like programming, but can’t understand basic things like what code comments are.

>They’re supposed to be exceeding human intelligence, at least at things like programming

This perception is a good part of why this market is irrational. LLM's aren't "intelligent". They do not reason, they are a very fancy kitbash of whatever it trains on.

Ad yeah, I'm not surprised that a lot of documentation on every bit of readable code online is awful. "Document the diff" sounds like an anti-pattern learned from people with an incentive to get as many PR's submmitted as possible, not make the most friendly documentation for people maintaining a project.

Re: AI;DR (AI; Didn't Read)

#488

Post by soupspaces »

ulrikrasmussen wrote: post #434
aaaronic wrote: post #252

Earlier quoted context omitted.

My "favorite" Claudism is when I critique its work and ask it to remove some unnecessary part of the design -- and then the diff has more green than red because it added comments about why the code is no longer there -- the code that was never in the mainline and never asked for!

This is a common problem, and I don't get why LLMs have not been tuned to stop this nonsense. It is writing comments as if the audience is you, the user in the session, while obviously code comments are meant for future readers.

Follow the tokens

Re: AI;DR (AI; Didn't Read)

#489

Post by atomicnumber3 »

stronglikedan wrote: post #248
delecti wrote: post #170

Earlier quoted context omitted.

It's not the ocean, it's the poster's own team. A simple "AI comments suck" in a sprint retro would be trivially easy and would at least start the conversation.

Doesn't matter. You'll come off as the baddie. It's the foreseeable future. Best just to learn how to interpret AI generated shit, or learn how to run it through AI and have it translate it to a more concise format without all the buzzwords. It'll take getting used to, but it'll save your career.

The number one rule of corpo programming: never, ever solve a problem you haven't been asked to solve.

Re: AI;DR (AI; Didn't Read)

#490

Post by febusravenga »

dragontamer wrote: post #439
stronglikedan wrote: post #248

Earlier quoted context omitted.

Doesn't matter. You'll come off as the baddie. It's the foreseeable future. Best just to learn how to interpret AI generated shit, or learn how to run it through AI and have it translate it to a more concise format without all the buzzwords. It'll take getting used to, but it'll save your career.

Bring it up in a bar or otherwise off work. There's a reason 3rd places exists. There's a social construct that off-work discussion (even when on-work) stays off work. If your coworker is professional and cares about keeping channels open, they too will respect the unspoken rules that govern 3rd place neutral locations. Blame it on the alcohol later on if it actually pisses someone off.

This is the third place. There is no real 3rd place in real companies usually. Not in mine, when i work remotely for company from other side of continent.
Post reply on HN