If there's one recommendation I'd give to podcasters it's to repeat the name of a book, blog post, movie, videogame, etc., that they're gushing on about. Don't refer to it as "it". Name it at least 3 times. If I'm driving and I missed the name, I want to hear it again.
Half off all books at @ManningBooks for the next couple of days! It's a great opportunity to buy Grokking Simplicity, my book on functional programming.
ericnormand.me/gsm
I always thought logic programming was about letting you specify the "what", and not the "how"... but SICP has a more nuanced explanation.
It's about letting you *separately* consider the what and the how, in isolation from each other.
sarabander.github.io/sicp/ht…
reading the intro to @EricNormand's book Grokking Simplicity, about Functional Programming
& struck by how yesterday I wrote a function that asks an LLM to make some decisions, and how it:
a) doesn't run the same way each time
b) has the side effect of costing 10-70¢
Pet peeve! When you see code like this:
const a = await someAjaxRequest();
const b = await someOtherAjaxRequest();
display(a);
display(b);
You can't display a until after b finishes! You're using a concurrent system but not taking advantage of the parallelism. Instead ...
...you're probably better off awaiting later where the value is used:
const aPromise = someAjaxRequest();
const bPromise = someOtherAjaxRequest();
display(await a);
display(await b);
Or...
... using promises directly:
someAjaxRequest().then(display);
someOtherAjaxRequest().then(display);
The former maintains order, the second one displays them as they come in.