What is a null coalescing operator but a poor man’s monad?
What is a pipeline operator but a poor man’s method call?
Posts by chreke
Spotify: open.spotify.com/episode/7l3T...
Apple Podcasts: podcasts.apple.com/se/podcast/f...
YouTube: youtu.be/sYqUUYlm4HU?...
RSS: anchor.fm/s/10395bc40/...
The Func Prog Podcast is back with another episode! I sit down with Adam Tornhill, the founder of CodeScene, to discuss technical debt, Clojure, and why it’s so hard to write good code.
Listen below! 👇
F35 ran into an CAS A-10 squad leader and got brutally airframe mogged
A pretty straightforward solution in Python:
Another programming puzzle for the weekend! programmingpuzzles.com/puzzles/013-...
Let's see your answers in the comments below!
People on twitter will really be like "you believe in writing raw SQL? that pales in effectiveness to my strategy, using a model abstraction layer so I can switch RDBMS at any time" and then never switch RDBMS
these just keep getting more insane—love it! 😂
A brute-force solution in Python
Are you ready for this week's programming puzzle? Share your solutions in the comments! programmingpuzzles.com/puzzles/012-...
Tickets for Func Prog Conf 2026 are live! 🥳 We sold out last year—get your ticket while they’re still available!
funcprogconf.com
if you want to write really clean code, you need to use vim
man, that’s crazy!
Thanks for coming on the podcast, very happy with how the episode turned out!
That sounds interesting! To me, these ideas are pretty much isomorphic—if I can put application logic in the database that is fine too
Spotify: open.spotify.com/episode/44bo...
YouTube: www.youtube.com/watch?v=IW-p...
Apple Podcasts: podcasts.apple.com/se/podcast/1...
RSS: anchor.fm/s/10395bc40/...
What better way to start your weekend than a new episode of the Func Prog Podcast? In this episode I talk with @giacomocavalieri.me about the @gleam.run programming language—we had a great time and covered a bunch of interesting topics!
Links in comments 👇
Here's my modest proposal: Stop moving data between your application and the database; instead, move the database into the application. Use a low-level store (e.g. RocksDB) for persistence and language-level primitives for concurrency control (a good use case for Rust?)
Since the database code can't "see" the application code (and vice versa), it's very easy to introduce deadlocks, race conditions, etc. Static analysis is of little help here.
SQL is convenient for fetching data, but its concurrency primitives are lacking. What's worse, the application and the database need a shared understanding of what resources are owned by whom. This creates a lot of ugly, brittle code.
Hot take: We need to rethink how we build distributed systems (read: web apps). The old three tier model of client–app server-database needs to go. For basic use cases it works well enough, but as soon as you introduce complex transaction logic, or high load, it breaks.
Time for another programming puzzle! Share your solutions in the comments!
programmingpuzzles.com/puzzles/011-...
chat, how cooked am i?
gnu reports AGI has been achieved internally
that feeling when your conference talk is rejected
I would be very interested! My company might be interested in helping out somehow (organization / sponsorship) if budget / time permits