HNHacker News
TopNewBestAskShowJobs

perrygeo

3,193 karma · joined April 28, 2014

submissionscomments
perrygeo··on California farmers are struggling to sell grapes as demand for wine drops
There's just no compelling reason to use alcohol anymore.

It used to be a universal social lubricant, but now people stay home - the only people drinking in public are drunkards. Not a great look.

It used to be considered "healthy" to drink a bit. Twenty-one drinks a week was considered normal. Now we have decades of research meta-analysis concluding, in no uncertain terms, that the only safe amount of alcohol is zero. https://hsph.harvard.edu/news/alcohol-is-the-root-of-62-dise...

Alcohol increases anxiety. Given the zeitgeist and state of the world, it's not surprising consumers want to avoid spiking their cortisol in the evenings.

Alcohol is expensive. The cost of living is going up and wages are not. The budget has to adjust somehow - alcohol is an obvious place to make cuts.

Alcohol prevents the body from metabolizing real food. Fat burning stops while the metabolism shifts to rid the body of the toxins you just dumped in. Aside from the health impacts, you're gonna see this directly in your gut circumference via visceral fat. Considering the GLP-1 trend, beer gut is out of fashion.

So for me personally, and anyone else paying attention, there is no reason to touch alcohol. It's strictly poison and has no valid role in a human diet. Sorry farmers - maybe switch to growing something that provides nutrition and isn't toxic?

perrygeo··on What makes Lisp difficult to read?
Of course it's a single data point, stating my personal preference and the objective characteristics of the code that make it more readable, to me. That's what the article did too! But they tried to use their biases to establish a claim on objective truth. That's the difference - I'm not trying to make a generalizable scientific claim!

I'm trying to say that making such claims in the first place is invalid.

There is no language that is objectively more or less readable. Yes, I've read the studies. No, none of them come close to adequately addressing the confounding factor of prior exposure/education. A randomized controlled trial starting from childhood could establish such truths, but such an experiment has not been done. Until then, small-n studies that don't address this flaw in any way yet continue to make broad claims - "pop" science is perhaps not dismissive enough.

perrygeo··on The problem is not AI code, but not knowing about system architecture or intent
> This gave me pause. Who had actually made the decision then? Arguably there has been several layers of human review, but the actual source of the decision was hard to pin down.

Cynically, this might be the real reason managers and investors love AI. It diffuses responsibility. No one is accountable. "Oops the AI messed it up" is a convenient excuse for bad management.

perrygeo··on What makes Lisp difficult to read?
> I have not yet encountered a fully satisfying explanation as to why Lisp is perceived as being less readable.

Difficulty is, by definition, relative to one's skill. You cannot so quickly discount the fact that 99% of programming is taught in Java/C style language syntax. If you've had lifelong exposure to Lisp, you might feel exactly the opposite. The author does a poor job of justifying why these pop-cognitive-psych theories should have more weight than prior exposure.

Personally, as someone with decades of exposure to both styles, I look at the factorial example and see everything I love about Lisp syntax - consistent, no magic keywords and syntax to memorize, it represents a tree just like my mental model of code, there's no way to fall through and forget an else, expressions instead of statements, no early returns ... literally everything about the Lisp example is more readable to me. YMMV.

perrygeo··on Guitar amp and effects pedal built on the Waveshare ESP32-S3-Touch-AMOLED-2.06
> I'm never wasting money another guitar pedal again

I've heard that one before. This one is the last pedal, I swear :-)

perrygeo··on We Should Be Able to Change Our Languages
Like most comments here, I kinda throw up in my mouth thinking about all the weird DSLs that would come from unrestrained abstraction.

What about a slightly different angle: a custom language runtime? The language itself stays true to the original but you build your own custom compiler and dev tooling: an expanded stdlib, LSP, linting, formatting rules, build systems, test runners, package manger, host extension system, etc.

This is becoming somewhat of a reality in the Clojure world. https://clojure.cc/dialects/ lists ~30 languages which are recognized as "Clojure" but have radically different host environments. Of course Clojure has macros too so nothings stopping you from going overboard on the DSL weirdness.

I could see the following scenario: Your company picks Typescript. You evaluate Bun and Deno and others but nothing really works. You take the most promising one, build a little test suite to make sure it stays consistent with the language spec, fork it, and add the runtime features you need. Your dev team still writes Typescript but you have full control over the tooling and how that code works at runtime.

perrygeo··on Is your Postgres migration safe or not safe?
It's definitely a bug. It's often distributed systems timing where things are "eventually consistent", just not at the moment you indexed. It can also be manual sql clients or other applications connected but not coordinating with the app. Not that I recommend that microservice madness style of development, but I've had to support databases in those scenarios. Pitfalls abound if you want to enforce uniqueness only at the application layer.

In the worst case bugs, systems can hum along for years with silent consistency problems. Database columns that are assumed to be unique but aren't - the truth only shakes out when you CREATE INDEX. Then once you fix that, you've got to find why the app was doing it in the first place! Generally its better for the app to crash than to silently corrupt the database as it had been doing all along.

perrygeo··on Is your Postgres migration safe or not safe?
Locksmith is awesome, how am I just now discovering this?

Your comments re: database state are spot on. DDL can fail in subtle ways. It's not even enough to take a snapshot of the current state and validate; things can change under your feet.

Take adding a unique index on a column: a simple CREATE UNIQUE INDEX statement, right? But you realize it will fail if the values aren't unique already, so you run a SELECT query to confirm. Yep, all unique. Deploy the app which runs the migration on startup - fail. A non-unique key arrived in the time between your queries.

Even more fun if you CREATE UNIQUE INDEX CONCURRENTLY and a non-unique key arrives in the middle of the DDL execution.

perrygeo··on Show HN: Modos E-Ink Screen Framework 13 Laptop
Awesome! I've replaced my desktop monitor with e-ink, and use an e-ink tablet for reading and browsing. My laptop is the final LED screen in my life. I don't know if I have the skills/time to DIY this but it looks promising. Great work!
perrygeo··on Is A.I. Above the Law?
It should be obvious. Yet here we are, with journalists telling sci-fi fantasy stories, read verbatim off the press-release.

It's not just obvious who's responsible, it's obvious who benefits from pedaling the "rogue AI" narrative.

perrygeo··on The Economics of Open-Weight Inference
I don't know about that. The frontier models have all sorts of strange regressions and quirks. They're more "intelligent" but, like hyper-intelligent humans who speak up without any skin in the game, I've found that they have a strong pull to add complexity to anything they touch. Truth is, I don't need frontier-level intelligence to write a CRUD app or debug my config file. The vast majority of software work is basic pattern matching.

Perhaps because they are dumber, they produce better results? IMO an excellent well-tuned harness combined with a "frontier minus x" model produces the highest quality result. DS4.1 and Qwen3.8, far from being a compromise, legit give me better results. For my personal definition of "better".

perrygeo··on AI coding has made CI a bottleneck, so we reworked ours to keep up
It's the difference between the value of "code" vs "software". Lots of people use those phrases interchangeably but its becoming painfully apparent that doesn't work anymore. Software requires more effort to actually make something IRL. Code can just be generated and sit in a repo, doing nothing, interacting with nothing.

Github has reported a 14x increase in code. Where did that 14x increase go? Certainly not to providing economic value - as you explained, we've basically flatlined there. It doesn't show up in revenue or profit margins. It doesn't show up in the app store metrics. It doesn't show up in speed or quality or security. It doesn't lead to new innovations or breakthroughs in software problems. All AI coding has done is to create more code.

The disconnect between 14xing code and barely 1.0xing software value is stark. It's not really an indicment on AI coding though. I think it reveals something interesting about the software industry. Specifically, that it was never about the code at all. It's about making that code do tricks in the real world - that's what constitutes almost the entirety of the value proposition. Code is cheap and getting cheaper. Software remains hard and is getting harder.

perrygeo··on MiMo v2.6
Can we afford to look past it? If/when claudeslop starts infecting every new model to such an extent, that model will produce its own slop, infecting new models... At what point do we lose all reliable methods for establishing "truth"? This is epistemic collapse waiting to happen. I honestly thought it would take longer... holding out for a coherent shared reality in 2030 seems optimistic.
perrygeo··on Study: BEVs emit 88g CO2/km over their lifecycle, less than half ICE cars [pdf]
They used initial manufacturing emissions + electricity emissions. But they forgot to incorporate tire wear. Any car will need at least one or two sets of new tires in its lifetime - and those are an incredibly energy intensive recurring cost.

Not to mention the asphalt roads we drive them on! Though that cost is shared by all drivers, it has to be accounted for somewhere.

Even if we have a 100% electric vehicle fleet, we'd still need oil to make roads and tires. Plus the 88g from the study. Since EVs are being sold as a way to "solve climate change", this is a big problem. Most people assume a transition to EVs would mean stopping oil. They are wrong.

perrygeo··on If AI coding is lowering your code quality, you're not managing quality right
I wonder if the definition of "code quality" needs to be updated? Consider DRY: There's a lot of cases where, if I was writing by hand, I'd prefer a succinct abstraction that's easier to type and reduces repetition - all good things right? Most developers, myself included, would gladly accept the complexity and runtime cost of a good abstraction if it saved them thousands of lines of boilerplate.

What about when repetitive typing is no longer a constraint? Do we need to pay for those abstractions? An LLM can scour the codebase and repeat patterns without getting tired. A simple-but-repetitive codebase might be ideal for an LLM.

This is one place I see AI coding changing the definition of code quality itself. I'm sure there are more...

perrygeo··on I think you should almost never use AI to write
Well, there's some nuance. I'm not really proud of my code. I'm proud of the software that gets built with it.

Code is just sitting in a git repo somewhere, not necessarily running. That's a big distinction for me. Consider that code volume has increased 14x on github this year, but we see nowhere near that increase in the actual usable software. Code is cheap and getting cheaper. Running software ain't.

Another way to put it: I'm only interested in code so far as the value it provides. That value, not the code itself, is the source of pride. If I can provide similar value without any code at all, I'd gladly do so.

perrygeo··on I think you should almost never use AI to write
I never use AI for writing but do so regularly for code. They are quite different to me.

My reason: code can be checked objectively. I can run it and confirm it works. I don't get attached to it. I don't feel pride in it (even when I write it by hand). Code just is. It's lifeless, inert, and entirely replaceable.

How do I do the equivalent for prose? How can I tell if my words "work"? Do they clearly convey my ideas to the intended audience? There's an element of subjectivity here forces me to identify personally with the prose.

Code has no such personality. I don't tie my identity or ego to code the same way I would an essay.

perrygeo··on War may be coming. Are we psychologically ready?
Deterrence is exactly what we should be doing. Many responses here were some variation of "he'd never try" or "let him try, we'd win". That's not deterrence - that's ignorance and provocation, respectively.
perrygeo··on The Hugging Face Hack Wasn't What It Was Cracked Up to Be
> Forget the ‘hive mind’ of AI agents ‘going rogue.’ They did what humans programmed them to do.

Finally, responsible journalism.

perrygeo··on War may be coming. Are we psychologically ready?
Read between the lines. He's saying "Mess with us, we'll nuke you." They mean it. Putin is desperate enough to do it. Anyone responding to this with Euro-bravado is an idiot. Some of y'all didn't grow up during the cold war and your blind spot is showing. No one wins in a nuclear war.
perrygeo··on There's no point at which turning your brain off will work
More commonly known as an "accountability sink". These existed before but it is so much worse with AI.
perrygeo··on Training a 4B model to produce 81% faster query plans than Postgres
Nice article about how to train/fine-tune a language model.

However, it misses the whole point of database query planning. You can't just ignore the planning time itself, as if the database query were a static entity to be optimized once at a leisurely pace.

The real constraint on live query planners is quite different: they must improve the combined time - planning + query - based on live database statistics. You can amortize the planning with prepared statements, but that too is fraught since optimal plans can change quite frequently and based on input parameters. "Live" and "faster than the queries themselves" are the hard requirements to be considered a viable database query planner. This project does neither.

perrygeo··on Why I'm still bearish on LLMs after Navier-Stokes
Asking a model to "write a throwaway program to do X" is vastly more productive and reliable than asking "do X". Running code provides a feedback loop, the model can iteratively improve the solution instead of guess. Even if you don't read the code yourself, you have a reproducible, editable, and auditable artifact if you need it.
perrygeo··on Aligned to whom?
The whole "alignment" angle is a farce. Not clear if alignment is even technically possible. But even assuming that, we're talking about "alignment" in a future full of well-adjusted humans where we prevent rogue AIs from getting loose. That's ... not what's happening. Everything we've seen so far indicates rogue humans acting against society, using AI a weapon to strip mine labor value and intellectual property.

So far, skynet continues to be a science fiction. I'm worried about what's actually happening. Every "rogue AI" story has a human behind it, either malicious or incompetent. And those people are the problem.

And not coincidentally, it's those same irresponsible sociopaths calling for regulatory capture and alignment.

perrygeo··on “Next-token predictor” is the wrong mental model for LLMs
Excellent article. Always upvote Phillip Ball!
perrygeo··on The contagion of fear
While I personally agree with the precautionary principle, when have we actually done that, as a society, in recent history? Fossil fuels, social media, industrial ag, and plastic pollution - there was barely a facade of precaution - post ww2 america has always been full Leroy Jenkins. The reckless approach to AI is right on brand.
perrygeo··on Detailed report on the use of solar geoengineering
In 2020 we eliminated sulfur dioxides from international shipping fuels to reduce pollution. We inadvertently did a little geoengineering project, albeit in the wrong direction. Pretty solid evidence that this sulfur removal had direct warming effects - https://www.nature.com/articles/s43247-024-01442-3 - For anyone needing a large scale demonstration of the climate-changing power of sulfur, this was it.

So the sulfur schemes are viable, in that they will block radiation and cool the planet. God knows what else it'll do - but the fact that sulfur works at scale and it's easiest option to try indicates that someone may attempt it before we understand.

I know it's a work of fiction, but check out Neal Stephenson's "Termination Shock". That's basically the plot.

perrygeo··on A Design Space Exploration of Async/Await
Amazing work. It's one thing to say "async is complex". It's another to parse that statement so carefully as to have a cross-language theory of async execution. Looking forward to digging into this!
perrygeo··on The UN challenges five centuries of cartography
Yes mercator distorts size at high latitudes. But it preserves angles which is more important for many (most?) mapping applications. Literally no one is using a mercator projection to determine size at the continental scale. We use mercator for navigation and for local maps. It keeps everything at right angles. Roads that run N-S look like vertical lines. If something is to the lower-left, that's south-west. These characteristics make it ideal for most maps.

The UN has only one mapping application - to equitably portray the world's country boundaries. In the larger space of potential maps, this is pretty niche. As a result, they need a niche projection.

perrygeo··on More questions about whether researchers can trust OpenAI with unpublished math
The stolen data claim isn't the smoking gun. We can already assume the frontier labs are accessing our data, as they have repeated done. Not news.

The big claim is that OpenAI sniped the research. Not a model, a human did so. Intentionally. They took someone else's idea and claimed it as their own. This is good old fashioned academic fraud, but with millions in compute resources and corporate incentives thrown at the problem.

← PreviousPage 2 of 34Next →