pgrust is ambitious but shall every developer build their postgres to prove they are good enough developers? The project claims to "show what Postgres would look like if it was built in 2026". It shows the traits yes: a single 3M line commit; no architecture discussion; no lessons learnt; claude it he top contributor; people writing emotional articles about why such projects are good.
It makes it really hard to connect to any of this. I loved danluu articles before, but somehow they've started to drift into this hard to grasp, hard to argue against shallow and empty world I try to get away from.
Interesting that you somehow start to talk about religion. I don’t think having a hypothesis about an eternal soul makes someone religious. Believing in “technology” or “technological advancement” seems to be a similar hypothesis as we clearly don’t see the future. The thing is that memories, input peripherals, the whole body is usually out of our conscious understanding so it seems to be a pretty farfetched idea that we operate in world where we don’t need pretty wild hypothesis about kinda everything without almost zero facts to depend on. Blue pill / red pill
Compare grep, sed, and your whole constellation of unix tools that accept characters on stdin and emit them on stdout and stderr; and where you can pipe them together. We can technically call them all 'next character predictors', despite their very different functions.
Don't confuse the stream for the function.
(Bonus: stick ```claude -p``` in your pipe if you want to watch modern tools mesh with traditional)
> Approaching it from first principles means starting with what we’re trying to do and asking how AI could help
I’m not sure why would you want to think about how an AI would help. If you understand what you need to do and you understand the capabilities of the tools available you run the coding / learning loop. If you think you should use AI then you are solving the how to use AI problem, which just adds to the complexity. Orthogonal to first principle thinking, just a workflow issue.
Is this a loaded question? People are getting hooked by high(ish) quality shows for relatively low prices. Once hooked you need to make them binge content (algorithm). Once hooked you can sell the ** for higher price.
It is called micromanagement when the boss tells you _how_ you should think. My approach is when leading a tech team to find together the things which should be done and find a method together to keep us on the path. Facilitation. Forcing decisions to be made. Keep quality high enough. Let people find what they enjoy doing and is useful. This is really basic and well known set of tools.
Quick feedback: this framework feels like a not so well thought out extension of polya’s how to solve it to “do things fast” in a credible looking way.
Harder feedback: the writeup feels like a quickly hacked together memo, which claims it is “self healingly” good. Because it has this throwaway quality I’m not sure what is the goal? Shall I engage with it seriously, when the lead dev didn’t seem to put in the effort? But if I don’t engage with it seriously it means that I have to follow this patchy fremwork?
I have aphantasia, figured out after a vivid dream which I’ve told my wife about so happily. She was not really amused. She sees these things ALL THE TIME. Like whenever she wants, or from time to time even when she doesn’t want to. She saw his father on the street one day. Two months after he had died.
We have a hard time communicating about things. She sometimes can’t express herself at all, she sees things she thinks I should be able to see. I have very good ability to remember schemata, maps. I move really quickly in pages and pages of text. I can summarize the pages and pages of llm output in less time than it is generated. She can easily put 8 grammatical mistakes in a 5 word sentence. We can communicate easily when i write the code quickly and she can checks the visual output in the browser, this is really fluid.
So now you have two vibe coded applications you don’t understand. I’m not an advocate of making “job security” decisions but this definitely goes to red flag territory. Was it your job to maintain the RN codebase or do you have other functions there as well? I’m not sure I would keep a native noob on a vibed native codebase. What is your take?
It makes it really hard to connect to any of this. I loved danluu articles before, but somehow they've started to drift into this hard to grasp, hard to argue against shallow and empty world I try to get away from.
reply