This is a fascinating talk by Gabriel Gonzalez at Haskell Love. It touches on several ideas I either mention or keep in mind (or wanted to explore!) in my MapCamp talk, Commoditisation and Programming Languages. Focusing on a strong language point, winning the position and from there expanding “vertically in the stack” as I think I mention in the talk is probably the best approach.
By Andres Löh at Haskell Love. Macros are powerful and dangerous at the same time. Sadly I didn’t fully grasp how to use staging fully from this talk, but knowing it is an option is good enough at the moment.
The leaders who have a low tolerance for risk — and I say leaders instead of managers because on engineering teams these concepts also apply to Staff and Principal engineers — will respond to risk by either avoiding it outright or figuring out how to spin the situation so that it is Not Their Fault(TM)
I have used similar approaches in other languages. Or at least what I understand as similar approaches (make a “human debuggable” version of what you want to do, then do it). Of course, there are Kan extensions here, which is kind of a next level 🤣.
It’s OK. If you can understand the behaviour model from the author, and combine that with small habits you get the gist. It’s one of those books that could be a long blog post, but it’s full of stories and tips. So, not bad but I still think Atomic Habits is the better of the habit books.
Interesting, although more precisely knowledge is compression. Thus, expression/teaching is compression too, since it is the transfer of knowledge. By the way, I saw that Picasso evolution in a neat Twitter thread. I wonder if David did see it. If you understand Spanish, it’s very well narrated. It has some comments pointing to similar evolutions (in particular to the Apple trees by Mondrian, some of my favourite paintings)
This sounds as a very tempting approach. Not because weekly reviews need a substitute, but because getting better at predicting and setting an expected value to what you put your time can help your decision-making (cf. Weekly Readings 51).
I had the idea of using Prolog to define a type system and explore languages… All has been invented, and this is super interesting. Worth noting the reference about the new type checker for Rust in a Prolog-ish dialect.
An interesting analysis (at a high StS level). I have beaten the game once or twice, getting the final Heart takes a while. An easy game to recommend by the way: hard enough to keep you engaged and simple enough to understand to be fun, if you know what I mean.
Python does the same for a set of small integers (from -5 to 120 something, if my memory serves). It can make a huge difference in many cases, since these numbers are commonly used as ranges in loops, and the impact on hot paths is significant.
One in 5,000 people has an inherited mitochondrial disease of some kind, with consequences that can include diabetes, vision and hearing problems, learning difficulties and other disorders.
As an alternative, he suggests that behavioral interventions based on mitochondrial function, such as exercise, could be the way to go. Exercise, he says, may be “the best thing you can do for your mitochondria.”