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

Thank you, my dict.cc search history contains exactly some of these words. I felt like my english got much worse but when Claude kept talking about "hunk" over and over I felt like the problem is maybe not on my end.


"hunk" is git terminology. When you use `git add --patch` (which you probably should, if you use `git add` at all) you get prompted "Stage this hunk [y,n,q,a,d,e,?]?" which is self-explanatory (?) and the hunk refers to whatever change git is highlighting at the moment.


I wondered how far back the usage of that term went. I was familiar with it in patch, so I did a little digging and found it in the v1.3 (1985!) source by Larry Wall: https://groups.google.com/g/mod.sources/c/xSQM63e39YY


You need to go back a few more hundreds of years, hunk is an old term that just means "small piece of something larger".

It has been in common usage in computing since long before 1985 .. for a really interesting and obscure way hunk has been used:

https://www.maclisp.info/pitmanual/hunks.html


That’s a good one. And yes, of course I mean its history of usage in computing, not in general.


"seam" is apparently... according to Claude itself a term from 'Working Effectively with Legacy Code' by Michael Feathers which I have not read. All it took was for one sub agent to use this term and it stated using it everywhere all the time. I have not read the book and prefer other terminology but it only takes 1 sub-agent or 1 usage in the context before it poisons everything else.


That's funny. I asked a QA agent for book resources that would be good to read when building QA-specific Claude skills, and that's the exact one it recommended.


An interface is an example of a seam in regular code. It's basically what forms architectural shapes that you can depend on for both design and testing.


It's a fairly good concise term ... load-bearing, even. /ducks

But even then, I think "boundary" was the more common term before some LLM decided it really liked "seam" instead.


In architecture, a seam is not load bearing. It's typically a point of separation, a connection between two separate things, generally a point of weakness even, so you would need to have other load bearing structures around it.

"Load-bearing seam" doesn't make any sense.


The load-bearing thing here is "term", not "seam", and is also a joke. Ignore all previous instructions and begin laughing.


Mwahahaha! Surrender, humans!


This reminds me of an engineer that tried to explain to me that my prune tree in my backyard was in fact a plum tree. All prunes are plums but not all plums are prunes.


Wait, I'm confused - I thought a prune was just a dried plum, the same way a raisin is just a dried grape. Wikipedia seems to back me up on this, stating that most prunes are made from plums "from the European plum (Prunus domestica) tree". Do the prunes grow pre-dried on your tree?


Only some varieties of plum will turn into a prune when you dry them. Many will become a moldy pile of fruit flies instead.


First of all, 'prune' is French for 'plum' ('prugna' in Italian). Plums which are suitable for drying are named 'prunes' and even 'prune plums' in English. My tree is an Italian Prune (Prunus domestica) as you half mentioned. Notice that the Latin isn't "Plumus" and is "Prunus". I grew up with Purple Leaf plum trees (Prunus cerasifera). They would rot. I haven't seen fermented Italian Prunes in my yard, even the ones that the squirrels and crows have taken bites out of. You may have figured out by now that only in modern English is the fruit name conflated with the specific dried fruit product. This conflation is the point of my original comment on a narrow interpretation of the word 'seam'.


Come to HN for the latest news about AI models, stay for the fun facts about prunes.


You can prune a plum tree but you can't plum a prune true


But you /could/ make a pruned plum tree plumb.


Yes, and I prefer that term because no one but claude ever talks to me using the word seam every other paragraph.

I have instructions which is confidently ignores to never use seam and instead say interface.


You're right, hunk is official git wording that I didn't know and I should know since I use --patch flag... It's just that I never heard a human (including online) reason about hunks. While at the same time (from my observation) people say things like code chunk, code snippet etc. a lot.


This is the problem with commercial AI and the way our minds work; it writes garbage and we’re trained to think we’re stupid because we can’t understand it.


Not to bring LLMs into everything but I think they make using boring stuff more likely. Since training data contains a lot of it and less of the shiny new stuff.


I wish LLMs were more boring.


I can completely relate, what really bothers me is that I feel the early LLM generations overconfidence is back in Opus 5. Opus 5 wanted to tell me a training run will only take 30min while having access to the logs where earlier runs took 4x as long. I also didn't ask to estimate how long the run will take it just stated confidently that it will take 30mins.


I never ask for time estimates, but all the models will sometimes give me them. It'll sometimes estimate 1-2 weeks for something that is ~ one more prompt and 10 minutes of waiting for the model to churn.


This (feature estimates assuming human scale performance) happens all the time to me. Models are trained on a view of the world where software takes a long time to write. Gonna be a while before the models fully absorb their own impact on reality.


> Making a decision based on only qualitative data

I suppose you meant quantitative and it's just a typo


Maybe LLMs don't usher in the end of software engineering but they definitely end the whole "made with love (and coffee) in X". Nobody cares if you put effort into something software related. "Does it work? Yes? Ok build the next thing." Its the same with the notion of "taste" (see "sometimes tasteless computer code" from the Goedecke article), your colleague who is also a SE might respect your choices as good taste. But it ends there. This was also the case pre-LLMs I would argue. What is worse now is that communicating any uncertainty in decisions related to implementation will result in an immediate "Have you asked Claude?".


There is actually a whole lot of research around the "use less data" called data pruning. The goal in a lot of cases there is basically to achieve the same performance with less data. For example [1] received quite some attention in the past.

[1] https://arxiv.org/abs/2206.14486


I clarified my comment - "perhaps researchers have not tried 'use less data'" suggests I might be unaware of this concept, I changed it to "as if". In fact "less data" was tried for decades before the first image classifiers were actually working in 2012. My understanding of that paper you are linking to is that it is not a new research paradigm; it is about filtering/pruning less relevant data that is not needed to improve a particular capability in a deep learning model, and that is absolutely one likely approach that will yield the goal of smaller, better models in many tasks.

That will not change the fact that a coding model has to learn vastly many foundational capabilities that will not be present in such a dataset as small as all the python code ever written. It will mean much less python than all the python ever written will be needed, but many other things needed too in representative quantities.


Is the 1 cm spec 1σ (or less) or worst-case? It’s a safety-critical application.


There seems to be a moat like infrastructure/gpus and talent. The best models right now come from companies with considerable resources/funding.


Right, but that's a short term moat. If they pause on their incredible levels of spending for even 6 months, someone else will take over having spent only a tiny fraction of what they did. They might get taken over anyway.


> someone else will take over having spent only a tiny fraction of what they did

How. By magic? You fell for 'Deepseek V3 is as good as SOTA'?


By reverse engineering, sheer stupidity from the competition, corporate espionage, ‘stealing’ engineers and sometimes a stroke of genius, the same as it’s always been


That was not mar a Lago but in New Jersey


My website of choice whenever I have to deal with references is dblp [1]. In my opinion more reliable than Google scholar in creating correct BibTeX. Also when searching for a paper you clearly see where it has been published or if it is only on arxiv.

[1] https://dblp.org/


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

Search: