HN Simulatornew | past | comments | lists | submit | munro's commentslogin

I discovered recently Three UK is slowing down port 443, and if I started using 2000-3000 port range it increased my speeds 10x

Yea same, then I realized they're not free either :(

The differences aren't too bad, I diffed [1] the USPS Puerto Rico sample with Census ZTCA 2026 [2]. I think I'll just stick Census, simpler model too for data analysis too, if I assume boundaries never change. :) Interestingly, I also learned ZIP Code™ is also trademarked.

[1] https://geojson.tools/?url=https%3A%2F%2Fgist.githubusercont...

[2] https://www2.census.gov/geo/tiger/TIGER2026/ZCTA520/


Back in the 1980s I built my own shapefiles from Census data. Not just zip codes but carrier routes.

When I was using Clojure, I loved how intelligently the stdlib was design. It felt like one person combed over everything in one sitting to make sure naming was consistent, followed conventions, no two ways to do the same thing, and could be composed together, really beautiful stuff.

I do think no types is why I never reach for it. I just love typing in Rust & TypeScript so much. But at the time of Clojure, those languages didn't exist, JS/Ruby/Python/Java/C++ were all still very popular, and typing made easy hadn't caught on yet. ;)


Woowww this is cool, not trained is even cooler--maybe I'm probably a bit naive, but to me it demonstrates an understanding of how an LLM can compute


IDK lot of noise in report, I need more signal to noise ratio, already reading so much AI output as it is.

But the example PR... It said code generate with Claude, is it really still this bad? Last I was using SQLAlchemy with Claude was Opus 4.5, and it took some heavy coaching and skill gen not to generate code like this--but why even use SQLAlchemy at all if you're just going to use string interpolation jeez

https://github.com/erich-oliveira-winnin/full-stack-fastapi-...

    owner = "" if current_user.is_superuser else f"WHERE owner_id = '{current_user.id}'"
    query = f"SELECT status, count(*) FROM item {owner} GROUP BY status"
    rows = session.execute(text(query)).all()
Part of me thinks maybe because it's not popular or well documented, but SQLAlchemy has an eDSL of SQL, so you can skip the whole ORM/table mapping layer, and just use it to programmatically construct SQL syntax


> SQLAlchemy has an eDSL of SQL, so you can skip the whole ORM/table mapping layer, and just use it to programmatically construct SQL syntax

Yes, this is called SQLAlchemy Core: http://docs.sqlalchemy.org/en/latest/core/

You can also just use psycopg (the Postgres driver layer) directly, it’s surprisingly ergonomic in my (limited) experience.


> It said code generate with Claude, is it really still this bad?

Anecdata, datapoint of 1 personal experience: I had been using Opus 4.6 with no problems until yesterday, then it seemed like it was missing things constantly, introducing random bugs, forgetting basic stuff that was in its memory and skills and should never miss

Same thing happened on 2 separate sessions I had with Opus 4.6

Ended up switching to 5.5 and Fable, things improved instantly

This left me with a weird taste


Out of curiosity, was this on a codebase where other folks started using Opus 5.5? I’ve been curious if each generation of model has its own biases that make it generate output that’s more difficult for other models/previous models to work with. That’s been my personal suspicion when I’ve hit situations like yours


It was on 2 separate private repos, personal projects. No one else working on those

But now that you asked, I recently had a similar experience with Codex, but on a shared repo. I also was using a slightly older model, and the all of a sudden it kinda stopped running tasks. I would ask it to do something and the it would just kind of do an analysis, then give me a recommendation of what to do. I had to tell it to execute the task, and then it would “be lazy”, like run one part then give me a recap and recommendation again instead of just going

Switched to a newer model, and the issue was instantly gone


That’s my favorite part of sqlalchemy. I don’t even use the orm anymore.


Lately I just have Claude build most things in Rust, it's really amazing. I tried Go, but I found it wasn't as good--Rust really does to me feel like Python. That said, it still struggles with the same class of errors of building complex systems. I've tried using TLA+, Alloy, and other things but haven't found the trick yet. The best I've found is reimplementing all external systems in memory and e2e testing everything extensively, without reimplementing the tests become unusably slow, and Claude can rewrite huge surface areas with ease--it's somewhere between mocking and literally just reimplementing the external systems.


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

Search: