Pinned Tweet
Here’s merge sort implemented in C++20 using only class template argument deduction guides
static_assert(false) retweeted
Every American should be outraged by what Trump has done to our nation's 250th birthday celebration. What should have been a once-in-a-generation moment to unite the country has been turned into another vehicle for division, propaganda, and political gain.
We uncovered how he hijacked America 250 – watch to see how.
This is precisely backwards
The only axis along which LLMs have not improved at all is in being confidently wrong about highly specialized details. If you are an expert in nothing you will feel unstoppable with LLMs while confidently producing broadly incorrect code
static_assert(false) retweeted
Replying to @bufftyf @sarthakgh
Most white collar jobs aren't even needed without AI being in the equation.
Something to keep in mind about LLMs is that with only partial view into the context (what we see on moltbook), “roleplay as a sentient robot” vs “I see everyone else on here is roleplaying as a sentient robot” vs <continuing a story about sentient robots> are indistinguishable
given the whole moltbook thing - once again re-upping the paper with the best model of “why did the llm do X?” arxiv.org/abs/2310.01425
> ultimate design pattern
> look inside
> global mutable variables
After 8 years of Haskell, 2 years of OCaml, 2.5 years of C++ and 45 minutes of Go, I present you the ultimate Design Pattern.
The Context Pattern
FP, OOP, Procedural and Declarative Programming combined to create The Last and Only design pattern you ever need.
A single record containing all your dependencies that you pass to every function explicitly.
No more inheritance.
No more classes and methods.
No more Dependency Injection.
No more singleton pattern.
No more private/public.
Mocks have never been easier.
This is the only pattern you need to structure EVERY SINGLE APP NO MATTER THE INDUSTRY (microservice, compiler, spaceship system).
AI companies *want* you to feel behind, like you’re in the passenger seat. But all of the progress of the last year has indicated the opposite; tools such as code review, doing well-specified bug fixes, and mapping code paths have gotten drastically better but…
I've never felt this much behind as a programmer. The profession is being dramatically refactored as the bits contributed by the programmer are increasingly sparse and between. I have a sense that I could be 10X more powerful if I just properly string together what has become available over the last ~year and a failure to claim the boost feels decidedly like skill issue. There's a new programmable layer of abstraction to master (in addition to the usual layers below) involving agents, subagents, their prompts, contexts, memory, modes, permissions, tools, plugins, skills, hooks, MCP, LSP, slash commands, workflows, IDE integrations, and a need to build an all-encompassing mental model for strengths and pitfalls of fundamentally stochastic, fallible, unintelligible and changing entities suddenly intermingled with what used to be good old fashioned engineering. Clearly some powerful alien tool was handed around except it comes with no manual and everyone has to figure out how to hold it and operate it, while the resulting magnitude 9 earthquake is rocking the profession. Roll up your sleeves to not fall behind.
And so maybe this is a hot take among my circles, but I do believe that there are effective uses of toolcalling LLMs today, but specifically where the *increase* humans’ understanding of their code (cross-referencing objdump and -Rpass eg) and not where they *decrease* our grasp
You can just laugh actually
You don’t have to be sad. You can just choose find things funny, like that you can #embed /dev/stdin in GCC >15
























