Live data from Hacker News

A few random notes from Claude coding quite a bit last few weeks

twitter.com

751–760 of 870 posts

Re: A few random notes from Claude coding quite a bit last few weeks

#751

Earlier quoted context omitted.

Which matches what they are. They're first and foremost pattern recognition engines extraordinaire. If they can identify some pattern that's out of whack in your code compared to something in the training data, or a bug that is similar to others that have been fixed in their training set, they can usually thwack those patterns over to your latent space and clean up the residuals. If comparing pattern matching alone,…

>"Reasoning", however, is a feature that has been bolted on with a hacksaw and duct tape. What do you mean by this? Especially for tasks like coding where there is a deterministic correct or incorrect signal it should be possible to train.

it's meant in the literal sense but with metaphorical hacksaws and duct tape.

Early on, some advanced LLM users noticed they could get better results by forcing insertion of a word like "Wait," or "Hang on," or "Actually," and then running the model for a few more paragraphs. This would increase the chance of a model noticing a mistake it made.

Reasoning is basically this.

Re: A few random notes from Claude coding quite a bit last few weeks

#752

Earlier quoted context omitted.

That's not true. Many technologies get more expensive over time, as labor gets more expensive or as certain skills fall by the wayside, not everything is mass market. Have you tried getting a grandfather clock repaired lately?

Repairing grandfather clocks isn't more expensive now because it's gotten any harder; it's because the popularity of grandfather clocks is basically nonexistent compared to anything else to tell time.

Doesn't need to be any particular reason to disprove the notion that technology only gets cheaper.

Re: A few random notes from Claude coding quite a bit last few weeks

#753
post #277
post #186

Earlier quoted context omitted.

The latest iphone has gone down in price? It's double. I guess the marketing is working.

"Pens are not cheaper, look at this Montblanc" is not a good faith response. '84 Motorola DynaTAC - ~$12k AfI (adjusted for inflation) '89 MicroTAC ~$8k AfI '96 StarTAC ~$2k AfI `07 iPhone ~$673 AfI The current average smartphone sells for around $280. Phones are getting cheaper.

Phones, or smartphones?

Re: A few random notes from Claude coding quite a bit last few weeks

#754

Earlier quoted context omitted.

yes, but people just really like to predict dooms and they also like to be convinced that they live in some special era in human history

It takes about 30 seconds of thinking and/or searching the Internet to realize that people also predict doom when it actually happens - e.g. with people correctly predicting that TikTok will shorten people's attention spans. It's then quite obvious that the fact that someone, somewhere, predicts a bad thing happening has ~zero bearing on whether it actually happens, and so the claim that "someone predicted doom in th…

There is always some set of people predicting all sorts of dooms though. The saying about the broken clock comes to mind.

With the right cherry picking, it can always be said that [some set of] the doomsayers were right, or that they were wrong.

As you say, someone predicting doom has no bearing on whether it happens, so why engage in it? It's just spreading FUD and dwelling on doom. There's no expected value to the individual or to others.

Personally, I don't think "TikTok will shorten people's attention spans" qualifies as doom in and of itself.

Re: A few random notes from Claude coding quite a bit last few weeks

#755
post #421

Earlier quoted context omitted.

Humans run hot too. Once you factor in the supply chain that keeps us alive, things become surprisingly equivalent. Eating burgers and driving cars around costs a lot more than whatever # of watts the human brain consumes.

I mean, “equivalent” is an understatement! There’s a reason Claude Code costs less than hiring a full time software engineer…

(it's VC money burn)

Re: A few random notes from Claude coding quite a bit last few weeks

#756

Slopacolypse. I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media. Did he coin the term "slopacolypse" ? It's a useful one.

I prefer slopocalypse.

not aslopalypse?

Re: A few random notes from Claude coding quite a bit last few weeks

#757
post #105

Earlier quoted context omitted.

The value extortion plan writes itself. How long before someone pitches the idea that the models explicitly almost keep solving your problem to get you to keep spending? Would you even know?

That’s far-fetched. It’s in the interest of the model builders to solve your problem as efficiently as possible token-wise. High value to user + lower compute costs = better pricing power and better margins overall.

> It’s in the interest of the model builders to solve your problem as efficiently as possible token-wise. High value to user + lower compute costs = better pricing power and better margins overall.

It's only in the interests of the model builders to do that IFF the user can actually tell that the model is giving them the best value for a single dollar.

Right now you can't tell.

Re: A few random notes from Claude coding quite a bit last few weeks

#758
I am developing a web application for a dictionary that translates words from the national language into the local dialect.

Vibe coding and other tools, such as Google Vision, helped me download images published online, compile a PDF, perform OCR (Tesseract and Google Vision), and save everything in text format.

The OCR process was satisfactory for a first draft, but the text file has a lot of errors, as you'd expect when the dictionary has about 30,000 entries: Diacritical marks disappear, along with typographical marks and dashes, lines are moved up and down, and parts of speech (POS) are written in so many different ways due to errors that it is necessary to identify the wrong POS's one by one.

If the reasoning abilities of LLM-derived coding agents were as advanced as some claim, it would be possible for the LLM to derive the rules that must be applied to the entire dictionary from a sufficiently large set of “gold standard” examples.

If only that were the case. Every general rule applied creates other errors that propagate throughout the text, so that for every problem partially solved, two more emerge. What is evident to me is not clear to the LLM, in the sense that it is simple for me, albeit long and tedious, to do the editing work manually.

To give an example, if trans.v. (for example) indicates a transitive verb, it is clear to me that .trans.v. is a typographical error. I can tell the coding tool (I used Gemini, Claude, and Codex, with Codex being the best) that, given a standard POS, if there is a “.” before it, it must be deleted because it is a typo. The generalization that comes easily to me but not to the coding agent is that if not one but two periods precede the POS, it means there are two typos, not to delete just one of the two dots.

This means that almost all rules have to be specified, whereas I expected the coding agent to generalize from the gigantic corpus on which it was trained (it should “understand” what the POS are, typical typos, the language in which the dictionary is written, etc.).

The transition from text to json to webapp is almost miraculous, but what is still missing from the mix is human-level reasoning and common sense (in part, I still believe that coding agents are fantastic, to be clear).

Re: A few random notes from Claude coding quite a bit last few weeks

#759
post #11

> LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building. I’ve always said I’m a builder even though I’ve also enjoyed programming (but for an outcome, never for the sake of the code) This perfectly sums up what I’ve been observing between people like me (builders) who are ecstatic about this new world and programmers who talk about the craft of programming…

> > LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building.

> I’ve always said I’m a builder even though I’ve also enjoyed programming (but for an outcome, never for the sake of the code)

> This perfectly sums up what I’ve been observing between people like me (builders) who are ecstatic about this new world and programmers who talk about the craft of programming, sometimes butting heads.

That's one take, sure, but it's a specially crafted one to make you feel good about your position in this argument.

The counter-argument is that LLM coding splits up engineers based on those who primarily like engineering and those who like managing.

You're obviously one of the latter. I, OTOH, prefer engineering.

Re: A few random notes from Claude coding quite a bit last few weeks

#760
post #234

Earlier quoted context omitted.

> far-fetched Remember Google? Once it was far-fetched that they would make the search worse just to show you more ads. Now, it is a reality. With tokens, it is even more direct. The more tokens users spend, the more money for providers.

> Now, it is a reality. What are the details of this? I'm not playing dumb, and of course I've noticed the decline, but I thought it was a combination of losing the battle with SEO shite and leaning further and further into a 'give the user what you think they want, rather than what they actually asked for' philosophy.

As recently as 15 years ago, Google _explicitly_ stated in their employee handbook that they would NOT, as a matter of principle, include ads in the search results. (Source: worked there at that time.)

Now, they do their best to deprioritize and hide non-ad results...

Post reply on HN