Something that occurred to me the other day is that AI has turned writing high-quality software from a P problem into an NP problem. Writing high-quality software used to be (in a loop): (1) Read and understand a large, complex, and probably messy codebase (2) Formulate a problem (3) Design a solution for it (4) Implement a solution for it that fits well into existing contours (5) Verify that solution, and goto (1-4) if more iteration is needed This is the process now: (1) Formulate a problem (and describing it to the AI) (2) Verify the solution that the AI gives you, and goto (1) if more iteration is needed Some people seem to think that (1) is the whole name of the game now. This is COMPLETELY missing the point of the tool, though. It's supposed to get rid of the polynomial-time part of the software-development lifecycle. It's not supposed to make it O(1), and pretty much all of the AI-slop trash I see go by has clearly never had a human actually look at what it's producing. None of this is surprising I guess, but if you consider yourself to be a strong engineer and tend to hold a high bar, I think it's very important to bear this in mind. ""Prompt engineering" and "context window engineering" are important (those are encapsulated by (1) above), but you have to also do the verification and meaningfully look at what's coming out the back end of the AI to fully bake what it's giving you. It's kind of baffling to me that people don't do this, because you can still 10-20x your productivity, _and_ produce even better-quality code than you were before. It would be like someone deciding to bake 1000 cookies to 60% done instead of baking 700 cookies to 99.99% of the way done, when before you used to bake a batch of 24 to 100% of the way done in the same amount of time.

Ironically, this account is the epitome of AI trash slop. Nvidia hasn’t done a large layoff since 2008. Why would they start laying people off now when their company is in the stratosphere and at the epicenter of the AI boom?

Does someone want to remind this cretin that a huge portion of the US military runs on an OS invented and given away for free by a Finnish guy who now resides and pays taxes in the US?

Finally got a chance to start reading @hahussain’s The Arab Case for Israel. Imagine my surprise when he describes attending a Yom Hazikarok celebration at B’nai Israel Congregation in Maryland, where I was Bar Mitzvah’d, and whose head Rabbi officiated my wedding. Small world, and it was quite moving to learn that it played a small role in the journey of such an intellectual powerhouse of the Middle East.

CachyOS has an awesome community around perf. They were the first distro to embrace sched_ext by a country mile and are also very welcoming and collaborative. These numbers are impressive but not surprising.

I wonder if this guy used AI to write this tear-jerker hypothetical. AI is definitely going to be an apocalypse for the tech industry, but it’s not just new grads who are in danger. The people with ideas are going to be the ones who succeed. AI is an equalizer in that regard.

Appreciate the shout out! I should really dust off the blog and get it going again. Let me know if there are any topics you want to hear about. I was thinking something like, “How do things actually run on CPUs?”. Can go into instructions, schedulers, etc.

“So far Apple has yet to mitigate these issues even with being disclosed to the company last year.”

With the BPF Instruction Set Architecture (ISA) document now officially published as #RFC9669 read about the details the process of bringing the RFC document to fruition, and why it's important to standardize core components of the BPF ecosystem: ietf.org/blog/bpf-rfc9669/

I wonder if aliens in the sombrero galaxy realize that other aliens look at their entire galaxy and are like, “Lol that’s a sombrero”

The BPF Instruction Set Architecture RFC document is hot off the presses: rfc-editor.org/info/rfc9669. Thanks to the @ietf, and to everyone who participated and helped make it happen!

Very interested and excited to hear more details. I always assumed it was impossible to trace an inlined function because the compiler can do basically anything with it, including e.g. eliding it completely. Daniel knows this though, so I’m keen to see what he’s cooked up!

Very early is an understatement. @CachyOS started supporting us soon after the first RFC patch set, which is honestly wild. A special community to be sure.