
I do physics, game design, software and startups. CTO https://teapawt.org/t.co/0vyZH2VCoq. Prev: collab with @DavidDeutschOxf, @Synthesischool, https://teapawt.org/t.co/2kAaTlfkjR
London, England
Joined February 2015
- Tweets2.1K
- Following732
- Followers707
- Likes7.2K
This @vgr classic is a great exposition of the opportunistic approach to life. ribbonfarm.com/2007/12/05/th…
62
This has implications for good collaboration!
‘There are no bad ideas’-style brainstorming is too lightweight because ideas need criticism to thrive.
But the presence of strong criticism shouldn’t stop your group pursuing an idea for a time if it is somehow interesting.
“Always, one should think carefully about when to expose an idea to criticism.
If one does it too early, it may cut off lines of thought which although false, would lead to something true if one pursued them seriously.”
— @DavidDeutschOxf
2
106
It was already knowable that the career headwinds for starting-out software engineers would be temporary due to the logic of society.
Felix shows an example of the revealing paths.
The coding interview is dead, at least for my team at Anthropic. I've seen enough to know that it no longer provides signal. I removed it from loops this month.
I have a spicy, optimistic take - I think there's an opportunity for junior engineers: felixrieseberg.com/hunger-be…
3
164
It’s a wonderful tool in a broad set of situations, many more than the undergrad who learns it in statistics class might imagine.
Yet despite popular ideological edifices supposing it generalizes all the way to the heart of rationality, it doesn’t.
While Eliezer was writing the sequences, Ken Binmore wrote a book called Rational Decisions, which was far more correct about the limited role of Bayesianism in rationality.
He ends it by expressing “fear that Bayesianism will roll on regardless”—alas, very presciently.
1
98
today I realized the DJ Wolfman Jack in Bob Dylan's Murder Most Foul stands for Alex Jones youtube.com/watch?v=3NbQkyvb…
135
Daniel Martin retweeted
During covid I played Go reasonably seriously for about a year (had a teacher, studied puzzles, etc.) I didn't get especially good at Go, but here's what I learned about competence in general:
1/ Go teachers are adamant about forcing you *not* to say to yourself "ah that was dumb" and move on. Sometimes a move really is just dumb and it's good to vent. Usually though you can spend an hour studying your seemingly dumb move because (a) there is smtg very maladaptive about your instincts that needs to be beaten out of you, or (b) you don't understand something deep about the game, or (c) you have a wrong attitude that needs to be adjusted. So long as you don't face this you don't get better, and so it's absolutely essential to approach "insignificant" aspects of the game with due reverence
2/ this has also been my experience teaching programming. Ppl hit some problem they don't understand and blindly tweak things until the program works (or ask an agent to do it), then go "ah that was annoying!" and move on. As long as they hold this attitude they don't get better, so they keep failing interviews then go on X and complain about leetcode. To get better it's essential to slow down and think very carefully, or better yet ask a good performer how they would have handled it in order to improve. (Today you can ask an agent "this is what I did to solve this problem and I think my approach keeps me from improving, how would a great programmer like person_i_respect likely handle it?" and get a pretty good answer!)
3/ in general your rate of improvement in Go is a function of your ability to notice your tiniest impulses and retrain yourself to convert them into productive action. These impulses are your boring run-of-the-mill cognitive distortions. For example, people will make instinctive moves because thinking is hard [effort aversion], hope the move works despite having no logical reason to expect that [magical thinking], then blame themselves when it doesn't work [learned helplessness]
4/ if you interview enough programmers or talk with enough startup founders you notice that poor performance is often a consequence of these same errors. Talking to users is hard so people stick with their ideas and hope for the best. When the product keeps not working they think "eh, maybe I'm bad at this startup thing", and so on. CFAR workshops were supposed to train you to notice these distortions and do the right thing, but I'm not sure how well they worked. (My guess is not well, since it seems unlikely these kinds of changes can happen over a weekend)
5/ there is a lot of research on this stuff and the data shows that getting good at a game like Go or chess doesn't give you an edge in other domains (i.e. "far transfer" doesn't work). This mirrors my subjective experience. In about a year I improved at Go considerably, but it did not make me any better at e.g. debugging or solving programming problems. But I do think that's not the whole story
6/ I have no hard evidence for this but I subjectively feel I got better at learning itself, and I can now get better in other domains quicker than I otherwise would have. For example it *really* sunk in that I have to disqualify my ideas. So when at work I started talking to customers to plan product roadmaps, while I wasn't instantly better at talking to them, my PM game improved enormously over the next few months because I finally learned not to be easily seduced by my own ideas or delude myself with wishful thinking
7/ to give another example, novice Go players tend to be very embarrassed of their games (the rules are simple but operationalizing them is hard, so early games are a disaster). Go ppl have a proverb for this-- "lose your first 50 games quickly". Meaning since early games don't matter and nobody will ever remember them, you should just get them out of the way. It didn't permanently cure me of embarrassment or anything, but it really sunk in how silly it is to worry about being a beginner in public and that I shouldn't worry about that at all
8/ if you're hard-optimizing your time you probably should work on improving the skills you care about directly. But otherwise I'd recommend spending a year trying hard to get good at a competitive intellectual game. Chess or Go are good, but really anything turn-based with an objective ranking you can't lie to yourself about. Pick whatever you're attracted to, try hard to get better, and keep mental notes about the process of learning that you can maybe apply to other domains later. At the very least it'll be loads of fun
9/ you will be humbled. No matter how smart you are or how hard you work you will discover the ceiling is infinitely high and there is an endless supply of people better than you. Getting that kind of humility has always been good, and it'll be especially good as AIs surpass us in basically everything. The sooner you get that out of the way, the sooner you can focus on a creative niche where you have no competition (since nobody can be a better you than you)
10/ you should probably stop after a year or two. Competitive games with an infinite skill ceiling can take over your life, don't forget to keep things in perspective
Daniel Martin retweeted
The list of “things I believe” from Nat’s website is always worth reading
something most folks who use muse won't ever know or appreciate was the degree to which this was @natfriedman's baby.
it has been one of the great honors of my career watching nat cook. he assembled and ran the team, and so many of the little details that people love came from his beautiful mind.
nat is one of the great artists of our time with products as his medium. more people should experience his brilliance, and with muse, they can ❤️
Terence Tao on using AI for math
“AI-maintained, out of necessity”
teorth.github.io/tao-web/ai-…
1
186
…to unite around our core values and objectives, and reject irresponsible and unsustainable usages of AI technology that only serve to advance nominal goals rather than the true underlying goals of the field.”
1
54
Reminds me of @DavidDeutschOxf’s point that solving a longstanding problem you love can be something of a disaster in practice.
It’s good we’re thinking deeply about how we should relate to math discoveries. Prizes were always a little crude.
25
This, but for more things: marginalrevolution.com/margi…
160
Daniel Martin retweeted
I started a blog in 2024 to write about ten technologies I wished existed. Today, I posted an update on them.
Nine out of ten are still unavailable. But I feel differently about that now:
blog.jacobtrefethen.com/half…
Nice reflections by @dhh on the changes in how computer code is created. youtube.com/watch?v=z4BzWpgy…
1
190
Daniel Martin retweeted
𝗦𝗮𝘁 𝟱
calling all optimists 🌞
hundreds of them in hyde park for the optimistic picnic - frisbee, a speakers corner takeover, a family zone, and whatever food and booze you bring.
LFG 🚀
@isnit0, @lfg_uk, @sotalikesfuture, @londonmaxxing, yours truly and more rocking up
lu.ma/pic-nic
Being deeply analytic, yet without fooling itself into thinking it’s built from first principles, is why I love recommending to study it.
I was attracted to theoretical physics (at least partly) due to a rationalist instinct: I believed that knowledge would be built from first principles, and physics seemed like the discipline most committed to doing that.
My most insightful takeaways:
- Scale separation: Theories don't need to be complete to be useful. A description can work extremely well at a narrow domain/scale, even if it clearly fails outside of that.
- Too-down thinking: When first principles are unavailable, you can begin with how a system behaves and work backwards towards a theory that explains it.
- Accepting uncertainty: Knowledge is approximate and uncertain. Things will almost certainly break down/fail at some point.
2
385













