Lisps are hardly my favorite languages, but the whole point of s-expressions is that it is a uniform syntax, which makes metaprogramming much, much easier. Metaprogramming is kind of the whole thing of lisps.

I’m not sure what you mean by “standard DB queue” (perhaps you mean a message queue, I guess?), but yeah Redis (or really, Valkey, now, since Redis tried to change license on everyone) is a very important tool in the toolbox for system design. In-memory databases trade persistence guarantees for raw throughput, and are very well-suited for different workloads than a traditional database is. It’s great for caching, rate-limiting, realtime analytics, leaderboards… Basically anything with ephemeral data or data that can easily be reconstructed from some other source of truth. It’s an optimization tool that can significantly reduce the load on your primary application database for certain workloads (and achieve higher throughput).

Slop commenting. The litany of AI slop websites that have popped up, polluting search results. The absolute flood of AI slop pull requests being submitted to open source projects, to the point at which many open source maintainers are buckling under the weight of garbage being thrown their way. Bots everywhere. The list goes on and on and on.

The internet is already a dessicated husk of what it once was.

Like when my toddler says he hates a food that he has never tried.

I’m sorry to hear about your condition.

You can definitely interact with them a lot. Beyond imaginative play (which kids love), you can also give Legos all kids of movement with articulation/technic pieces. The possibilities are quite literally endless. There’s a reason that there’s so many adults that are Lego enthusiasts.

I’m saying that AI companies have repeatedly shown a flagrant disregard for licenses, contracts, and the law, and have engaged in massive theft. Why should we expect that any contract would actually be honored? The whole thing is a huge fucking grift.

Our interview process has the candidate implement a couple (extremely simplistic) API routes, with the specific approach left up to the candidate. It’s more about having something they can talk through and evolve than it is about us looking for any specific approach.

Basically it exists as a way for us to have a starting point for talking about scalability topics, asking the candidate how they would evolve their implementation as we scale up the system. Does a pretty good job of giving us an idea of how they think through system design problems.

I was not talking about your specific lawsuit, or TLS.

Companies trust other companies all the time, and it’s foundational to most all SLA/SLOs. Any time I’ve voiced concerns around how AI companies are using the data we are giving them (like giving them access to our codebase), it’s brushed off as “we have an agreement with them”. It’s just a load of hogwash. They can and will abuse all data they have access to, just as they have done thus far.

In this particular case, we are talking about a data center, and it is not at all reasonable to assume that the data that flows to said data center is in any way protected, especially one run by Musk.

Still means jack shit. Companies will lie through their teeth and violate any and all they can get away with.

They are not to be trusted.

I write code myself all day, as I have always done. And more and more software engineers are finally starting to see the consequences of relying on LLMs for software development.

Writing code has never been the bottleneck.

I do use quite a bit, but I also do a lot of different things. Compiling code, running docker containers, local web servers, an android emulator, slack, browser tabs for Jira/confluence/figma/etc., all adds up pretty quick.

8GB is definitely nowhere near enough, at least for what I need to do.

I’m worried about nix, honestly. An absolute truckload of nix packages pull their source from GitHub. It’s the primary way to distribute flakes, too.

I never understood how anyone found those remotely interesting. Maybe they’re just supposed to be funny but… I don’t know. I don’t get it. Always just seemed like taking an assortment of questions and stretching the implications of one’s answers to the point of incredulity in order to shoehorn them into one of the set outcomes.

Like a choose your own adventure book where the outcomes only have the faintest connection to your choices.

What the actual fuck, Guardian.

Did the headline change? The current headline is Torvalds: “100% of Their Code is Written by Compilers” Too

The title of this post makes for a dumb headline, at any rate. Linus, in response to claims in the industry that projects are now “99% written by AI”, drew an analogy to compilers by saying that all machine code for projects are written by compilers, yet no one says their project was 100% written by a compiler. It’s just talking about stupid hype, which is valid.

That being said, it’s still quite unfortunate that Linus has fallen into the trap of LLMs.

These people really are fucking delusional.

Umm I use Jira and Confluence on Firefox every day without issue. Not sure what you’re talking about. The only time I’ve ever had to use Chrome in my professional career were certain tools that require chrome dev tools. Otherwise, it’s Firefox for everything.

Seriously. My argument against “LLMs are good at generating boilerplate” has always been “why are you putting up with needing to write boilerplate in the first place?”

I really do think that it’s emblematic of a problem that existed long before LLMs: a lot of developers were/are deeply uncomfortable with stepping outside the confines of their IDE, and thus would basically never fix workflow/DX issues unless said fix came packaged as a feature by whichever megacorp was feeding them tooling. Scripting is all but unheard of outside of things like builds or CI.

I see this divide in my own organization, actually. Our mobile developers aren’t really all that comfortable with stepping outside of what Android Studio/XCode can do and the workflows deined by Google/Apple.

Our backend team is very different. No one uses IDEa, and we’re all Unix terminal folk for the most part. Lots of scripting and tooling we’ve created over time to streamline our development.

So when me and few other backend engineers decided to write a small Caddy file to set up a reverse proxy to enable the mobile emulators to talk to our locally-running backend (rather than a shared non-prod backend that the mobile teams always use, in order to facilitate more efficient end-to-end testing for features), we may as well have been talking an entirely different language when describing it. The very idea of creating your own tooling to solve a problem with your job is just entirely alien to them.

This is what happens when you don’t take a stand against this shit. He brought it on himself.