6,882 karma · joined August 20, 2020
contact: hn@kortlepel.com
If an LLM helps you do that, then use it.
Have you seen LLMs build large, stable, pieces of software, that work well, with your own eyes? I have not. I have seen LLMs build small, well-understood things, and I've seen LLMs do super well with extremely well specified problems, but all the rest seems to be marketing (i.e. I couldn't observe or reproduce it).
Edit: I'm not talking about throwaway slop that just needs to run long enough to get funding.
There's a git server, it's installed when you install git, and it really does work very well.
> every instance is a disposable cache that revalidates with one conditional GET. No database, no Redis, no gossip, no leader, no node identity.
Git famously doesn't use that either...? What is the point?
> "just put the repositories on NFS" failed at every large host that tried it
Yeah, that's a terrible idea. You can just host Git on a server or two. Where's the limit? How much does it scale to put a single 64 core server with a 10 gbit link on a local network and put ONLY git on it? Is that really that slow and bad? You can give it 20+ TB of RAID storage for VERY cheap. What is the limit you're hitting? 200ms ping to it from across the world? Is that the issue we're solving?
> walgit takes that as-is, and adds what a monorepo on small machines needs: serving refs and web pages for a repository whose packs will never fit on the instance (a remote reader over HTTP range requests), keeping commits and trees local while blobs stay in the bucket (the history pack), and moving clone bytes out of the server entirely (bundle-uri: fresh clones and catch-ups are static files the bucket or a CDN hands out).
So it's about monorepos that, for some reason, have blobs large enough to be impossible to serve via range requests, shallow clones, etc? Are people committing binary blobs of 1TB+ to their git? There's Git LFS, that hooks up an object store (like S3) to git for large files.
As an aside, I kind of adore that Tobi's latest post on his website, from 2019, talks about shopify's carbon emissions, meanwhile today his github is full of AI slop projects and enabling others to "vibe" even harder. He also missed that his clanker wrote an announcement post; https://github.com/tobi/walgit/blob/main/docs/announcing-wal...
There are a lot of ways to avoid exponentially more commits, issues, and PRs breaking your backend down, and begging every visitor and user to please use AI to write 40x more code that needs 40x more fixes is not one of them.
* Forgejo
Those are my favorites. Both you can self-host for your company, including CI/CD.
For tasks like pondering on something, reviewing code, etc. I use Pro, just because it feels like the right model for that.
I read it as a "hey we will make stuff more expensive, don't miss it"
TDD, OOP, Clean Code, etc are an attempt to solve very real problems. They are then applied as dogma to places where these problems are not evident. That's the issue. Of course these rules have their place, but always with a caveat and never applied over all possible places where they might fit. Very often, a better solution exists, as well.
This reduces the cycle time on issues and reduces bugs and performance regressions. If I pitched that last sentence to your boss, chances are he'd take it.
Yeah, I have a pretty good idea of how we go from code -> IR registers -> x86 registers and how the underlying hardware has more registers than that, etc.
As for SPARC and POWER, I have not yet gotten my hands on one! But as someone who writes compilers for fun I did learn about most of that, yes.
I write C# in my dayjob, and having written high-ish performance C++ and Rust for a couple years before that, and because of all the curiosity-driven projects I've done (like writing useless compilers), I did learn a lot.
This has helped me massively in my job, especially when optimizing our C# sensor data ingestion backend to process hundreds of thousands of measurements per seconds with explicit backpressure etc. it was great fun because I know what I'm doing.
I'm not trying to "uhm actually" you, but when you call yourself a software engineer, I do expect that you know some of these things after some years in the industry. The only way you wouldn't is a lack of curiosity, or because you genuinely had no idea that you CAN learn these things.
Try the Kö in Düsseldorf! Of course this is a jab at the fact that nearly every nice store there is one where you walk in, get profiled, and then are given champagne and asked to sit down before you can even look at clothes. We have this ridiculous shit, it's just localized to a couple places known for being so posh! :)
For any work with protected intellectual property, I use other providers, for the contractual guarantees, but I think it would be silly to think that OpenAI or Anthropic are not training on literally all data they get. How could you ever tell if they did? They can just claim the data was mislabelled, or ignore the accusations. If you have serious IP, use only local models.