Image Similarity - Procjam - Museum Labels - Shopify?! - RAG - Myrninerest - Quantum Magic

A scientific team has managed to stack 41 layers of semiconductors, multiplying the density of the circuits by six, without needing to make them any smaller

World Labs splats - Video Cats - Distributed Heroines - Among AIs - Historical Type - Reve

PinePhone Pro [GNU/Linux smartphone] has been discontinued L: https://social.treehouse.systems/@pine64/115027515081143369 C: https://news.ycombinator.com/item?id=45053872 posted on 2025.08.28 at 12:05:13 (c=0, p=5)

Here's a list of all the good first issues you can take on if you'd like to contribute to Agregore. If you see something that sounds fun, comment on the issue or ping @RangerMauve to claim it.

Recently the CEO of Github wrote a blog post called Developers reinvented. It was reposted with various clickbait headings like GitHub CEO Thomas Dohmke Warns Developers: "Either Embrace AI or Get Out of This Career" (that one feels like an LLM generated summary of the actual post, which would be ironic if it wasn't awful). To my great misfortune I read both of these. Even if we ignore whether AI is useful or not, the writings contain some of the absolute worst reasoning and stretched logical leaps I have seen in years, maybe decades. If you are ever in the need of finding out how not to write a "scientific" text on any given subject, this is the disaster area for you. But before we begin, a detour to the east. # Statistics and the Soviet Union One of the great wonders of statistical science of the previous century was without a doubt the Soviet Union. They managed to invent and perfect dozens of ways to turn data to your liking, no matter the reality. Almost every official statistic issued by USSR was a lie. Most people know this. But even most of those do not grasp _just how much_ the stats differed from reality. I sure didn't until I read this book. Let's look at some examples. ## Only ever report percentages The USSR's glorious statistics tended to be of the type "manufacturing of shoes grew over 600% this five year period". That certainly sounds a lot better than "In the last five years our factory made 700 pairs of shoes as opposed to 100" or even "7 shoes instead of 1". If you are really forward thinking, you can even cut down shoe production on those five year periods when you are not being measured. It makes the stats even more impressive, even though in reality many people have no shoes at all. The USSR classified the real numbers as state secrets because the truth would have made them look bad. If a corporation only gives you percentages, they may be doing the same thing. Apply skepticism as needed. ## Creative comparisons The previous section said the manufacturing of shoes has grown. Can you tell what it is not saying? That's right, growth over what? It is implied that the comparison is to the previous five year plan. But it is not. Apparently a common comparison in these cases was the production amounts of the year 1913. This "best practice" was not only used in the early part of the 1900s, it was used far into the 1980s. Some of you might wonder why 1913 and not 1916, which was the last year before the bolsheviks took over? Simply because that was the century's worst year for Russia as a whole. So if you encounter a claim that "car manufacturing was up 3700%" some year in 1980s Soviet Union, now you know what that actually meant. ## "Better" measurements According to official propaganda, the USSR was the world's leading country in wheat production. In this case they even listed out the production in absolute tonnes. In reality it was all fake. The established way of measuring wheat yields is to measure the "dry weight", that is, the mass of final processed grains. When it became apparent that the USSR could not compete with imperial scum, they changed their measurements to "wet weight". This included the mass of _everything_ that came out from the nozzle of a harvester, such as stalks, rats, mud, rain water, dissidents and so on. Some people outside the iron curtain even believed those numbers. Add your own analogy between those people and modern VC investors here. # To business then The actual blog post starts with this thing that can be considered a picture. What message would this choice of image tell about the person using it in their blog post? 1. Said person does not have sufficient technical understanding to grasp the fact that children's toy blocks should, in fact, be affected by gravity (or that perspective is a thing, but we'll let that pass). 2. Said person does not give a shit about whether things are correct or could even work, as long as they look "somewhat plausible". Are these the sort of traits a person in charge of _the largest software development platform on Earth_ should have? No, they are not. To add insult to injury, the image seems to have been created with the Studio Ghibli image generator, which Hayao Miyazaki described as an abomination on art itself. Cultural misappropriation is high on the list of core values at Github HQ it seems. With that let's move on to the actual content, which is this post from Twitter (to quote Matthew Garrett, I will respect their name change once Elon Musk starts respecting his child's). Oh, wow! A field study. That makes things clear. With evidence and all! How can we possibly argue against that? Easily. As with a child. Let's look at this "study" (and I'm using the word in its loosest possible term here) and its details with an actual critical eye. The first thing is statistical representativeness. The sample size is 22. According to this sample size calculator I found, a required sample size for just one thousand people would be 278, but, you know, one order of magnitude one way or another, who cares about those? Certainly not business big shot movers and shakers. Like Stockton Rush for example. The math above assumes an unbiased sampling. The post does not even attempt to answer whether that is the case. It would mean getting answers to questions like: * How were the 22 people chosen? * How many different companies, skill levels, nationalities, genders, age groups etc were represented? * Did they have any personal financial incentive on making their new AI tools look good? * Were they under any sort of duress to produce the "correct" answers? * What was/were the exact phrase(s) that was asked? * Were they the same for all participants? * Was the test run multiple times until it produced the desired result? The latter is an age old trick where you run a test with random results over and over on small groups. Eventually you will get a run that points the way you want. Then you drop the earlier measurements and publish the last one. In "the circles" this is known as _data set selection_. Just to be sure, I'm _not_ saying that is what they did. But if someone drove a dump truck full of money to my house and asked me to create a "study" that produced these results, that is exactly how I would do it. (I would not actually do it because I have a spine.) Moving on. The main headline grabber is "Either you embrace AI or get out of this career". If you actually read the post (I know), what you find is that this is actually a quote from one of the participants. It's a bit difficult to decipher from the phrasing but my reading is that this is not a grandstanding hurrah of all things AI, but more of a "I guess this is something I'll have to get used to" kind of submission. That is not evidence, certainly not of the clear type. It is an opinion. The post then goes on a buzzwordsalad tour of statements that range from the incomprehensible to the puzzling. Perhaps the weirdest is this nugget on education: > Teaching [programming] in a way that evaluates rote syntax or memorization of APIs is becoming obsolete. It is not "becoming obsolete". It has been considered the wrong thing to do for as long as computer science has existed. Learning the syntax of most programming languages takes a few lessons, the rest of the semester is spent on actually using the language to solve problems. Any curriculum not doing that is just plain bad. Even worse than CS education in Russia in 1913. You might also ponder that if the author is _so_ out of touch with reality in this simple issue, how completely off base the rest of his statements might be. In fact the statement is so wrong at such a fundamental level that it has probably been generated with an LLM. # A magician's shuffle As nonsensical as the Twitter post is, we have not yet even mentioned the biggest misdirection in it. You might not even have noticed it yet. I certainly did not until I read the actual post. Try if you can spot it. Ready? Let's go. The actual fruit of this "study" boils down to this snippet. > Developers rarely mentioned “time saved” as the core benefit of working in this new way with agents. They were all about increasing ambition. Let that sink in. For the last several years the main supposed advantage of AI tools has been the fact that they save massive amounts of developer time. This has lead to the "fire all your developers and replace them with AI bots" trend sweeping the nation. Now even this AI advertisement of a "study" can not find any such advantages and starts backpedaling into something completely different. Just like we have always been at war with Eastasia, AI has never been about "productivity". No. No. It is all about "increased ambition", whatever that is. The post then carries on with this even more baffling statement. > When you move from thinking about reducing effort to expanding scope, only the most advanced agentic capabilities will do. Really? Only the most advanced agentics you say? That is a bold statement to make given that the leading reason for software project failure is scope creep. This is the one area where human beings have decades long track record for beating any artificial system. Even if machines were able to do it better, "Make your project failures more probable! Faster! Spectacularer!" is a tough rallying cry to sell. To conclude, the actual findings of this "study" seem to be that: 1. AI does not improve developer productivity or skills 2. AI does increase developer ambition This is strictly worse than the current state of affairs.