@ericnormand
Account based inCanada
About this account
- Account based in
- Canada
- Connected via
- Web
Account-level information from X, not a live location or the device used for a specific post.
Learn Clojure & Functional Programming ☞ https://nitter.cf/t.co/oYnRibhoKr Author of Grokking Simplicity ☞ https://nitter.cf/t.co/zPmPNRgOhK
New Orleans
Joined May 2009
- Tweets21.3K
- Following569
- Followers7.6K
- Likes887
We're live! Apropos Clojure youtube.com/live/gfhlkUkYbe0…
We're talking with David Nolen on Apropos in 12 minutes!
youtube.com/watch?v=52lGEPWA…
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
Just about ready to go live! youtube.com/live/vfYB-5Z7gts… Apropos!! with Sean Corfield as a special guest.
The next Apropos is tomorrow with Sean Corfield!
youtube.com/live/vfYB-5Z7gts…
Apropos streaming next week with special guest Alex Engelberg: youtube.com/live/MF-A46cTYUY… @alex_engelberg
Apropos welcomes Alex Miller to the show today! m.youtube.com/watch?v=zkEZyk…
Catch us live!
Apropos broadcasts in one hour! With guest Zach Tillman
youtube.com/watch?v=9wN-uBnr…
Eric Normand retweeted
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…
Eric Normand retweeted
Be astounded and inspired by @ericnormand showing the leverage abstraction gives you at Heart of #Clojure: youtu.be/nX9AWZ0Xa-M
Eric Normand retweeted
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...