Live data from Hacker News

AI;DR (AI; Didn't Read)

rickmanelius.com

671–680 of 729 posts

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

#671

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…

[dead]

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

#672

Earlier quoted context omitted.

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…

Who'd want to work in an environment like this? It's not sustainable

Everyone who wants to eat and send their kids to college

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

#673

Earlier quoted context omitted.

It's not that it fundamentally isn't able to produce something concise, it's that the business model of the companies developing these models rests on selling tokens...

It’s not some conspiracy. If they knew how to make the AI responses better and more concise, they would. They just don’t yet.

I don’t know. The old models were much more concise, answering your question in a couple of sentences. At some point they just started outputting walls of text for every prompt.

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

#674

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…

The number of times I've seen phrases of the form "(ingestion|main|ingress|success|designated} path" in workslop docs recently is frankly intolerable. Last week someone sent me a 50 page doc with a proposed update to a (small) system architecture. It was so boring that it took me all day to read it, but the information density was low enough that it could have been written (by the author instead of a chatbot) in like 3 pages. Endless tables comparing the "recommended path" against stupid strawman implementations, and repeated "DO NOT send packets directly to the ingress, ensure they go through ..." statements that were totally unnecessary. Utterly mind-numbing thought-terminating slop.

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

#675

Earlier quoted context omitted.

Have you worked in corporate recently or at a particularly toxic one? Asking because when I was at capital one, certain comments or questions about topics like this, would actually get you noticed negatively by your manager and being disruptive to what leadership wants hurts your career. In fact being the one to ask and point out questions like yours ultimately got me PIP'ed and removed from the company. So, like, ye…

I grant that sane behaviors may not always be successful at toxic companies. That seems true by definition. But I don't think general career advice should be based on what is (temporarily) safe at the bottom decile. Also, if you go back you'll note that I didn't suggest that people "tell the truth". I suggested people ask a neutral question about an obvious phenomenon. If it's unsafe to give an honest answer, most pe…

Ah, I see. I didn't specifically think Capital one was toxic, though, more recently after sharing about my experience more I've been realizing it may have been.

I can see how that technique works great at a non-toxic company. Thank you.

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

#676

Earlier quoted context omitted.

I used to use em-dashes for explanatory clauses--like this one, for example--when using commas would make the sentence difficult to parse due to other nearby commas. They're only a LinkedIn-ism when used to create an unduly dramatic juxtaposition for an otherwise mundane idea. But now they set off people's AI radar when used for any reason at all.

Perhaps I am biased because I find the use of em-dashes without spaces (as is common in English typesetting) to be inherently ugly so I'm not too unhappy to see their use discouraged.

Same here. I was always more of an en-dash enjoyer, and used that back in academia since it's just a double-dash in Latex.

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

#677

Earlier quoted context omitted.

It's not that it fundamentally isn't able to produce something concise, it's that the business model of the companies developing these models rests on selling tokens...

because human writing IS not just producing the Next token, sometimes you write shit and then go back and find ways to improve and try to play tricks inside the structures only you or your coauthors understand. AI doesnt do this

Exactly! That's also why almost every slop commit I see has a linecount like +700 / -20, whereas human commits often end up net zero. I try to remove more lines than I add, if possible, but LLMs will just add more bloat, forever.

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

#678

Earlier quoted context omitted.

It's not that it fundamentally isn't able to produce something concise, it's that the business model of the companies developing these models rests on selling tokens...

It’s not some conspiracy. If they knew how to make the AI responses better and more concise, they would. They just don’t yet.

Bullshit. It would cost them more money to post process all the bullshit and then ship that, instead they just point the cannon at your face and pull the trigger.

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

#679

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…

[deleted]
Post reply on HN