Pieter Herroelen retweeted
I was convinced the next breakthrough in developer productivity was going to happen with a new programming language or paradigm.
I spent a few years learning lots of different languages - Erlang, F#, Haskel, Clojure, Golang and Rust, to name a few.
But the leap for developer productivity actually happened in the infrastructure layer instead 😅 So I was off by a few abstraction layers!
I don't use any of these languages anymore. But some of the best things about Erlang have made their way into the Lambda execution environment.
e.g. Lambda's worker instances don't share memory and can fail independently, similar to Erlang processes.
A Lambda worker handles one request at a time so you don't have to worry about concurrency in your code and dealing with concurrent updates to shared state.
This is similar to how Erlang processes work, with its message box concept.
If a fatal error happens, the Lambda worker automatically restarts the process and continues to serve the next request. Similar to the supervisor behaviour in Erlang.
Even if I don't get to use any of these languages, the learnings from them are still valuable.
I've taken something from each and they have helped make me a better software engineer than I would have been otherwise.
They help me recognize patterns, common problems and solutions. Many of which transcend abstraction layer boundaries.
So, don't feel bad about learning things that you don't get to use at work. Learning can be its own reward :-)
And with all the AI chatbots, it's easier to learn a new piece of technology than ever before.
Pieter Herroelen retweeted
Welcome to the public domain, STEAMBOAT WILLIE (1928)! archive.org/details/Steamboa…
Pieter Herroelen retweeted
One of the biggest tells that someone doesn’t know what they’re talking about: glossing over addressing resource constraints, or saying things that imply infinite resources. Effectively everything is resource-constrained, & seasoned practitioners are especially sensitive to this
Pieter Herroelen retweeted
For the past few months we’ve been working hard at implementing event sourcing. Why are doing that? Because the previous design had its limits and the next big feature would have exposed its flaws even harder
1
57
“The paradigm I’m fighting is structuralism.
We’ve been treating the world like there’s structured code behind it.” @barryoreilly at @ddd_eu #dddeu
Pieter Herroelen retweeted
"A COMPUTER CAN NEVER BE HELD ACCOUNTABLE
THEREFORE A COMPUTER MUST NEVER MAKE A MANAGEMENT DECISION"
Pieter Herroelen retweeted
"Do X without relying on engineers" is a core part of the marketing for way too many b2b SaaS products. It would be great if we could have an honest conversation about why this dynamic exists and why it's dysfunctional.
Time saved at a non-bottleneck is worthless — @EliGoldratt nextplatform.com/2022/12/13/…
30
Pieter Herroelen retweeted
X : You seem quite positive about ChatGPT?
Me : I've been very clear that this would be the next battlefield - nitter.cf/swardley/status/115799… - and for the first time, in a long time, AWS isn't first. OpenAIs focus on industrialising this space is fascinating and well played.
Pieter Herroelen retweeted
Talent isn’t the problem. The problem is the very idea of having a separate business organization. No one at Netflix or Amazon ever talks about “The Business”. —@adrianco #TheValueFlywheelEffect
Pieter Herroelen retweeted
RIP to the incredible Fred Brooks. 🙏🏼
Replying to @SteveBellovin @unccs
From en.wikipedia.org/wiki/Fred_B… about Fred Brooks: "The most important single decision I ever made was to change the IBM 360 series from a 6-bit byte to an 8-bit byte, thereby enabling the use of lowercase letters. That change propagated everywhere." May his memory be a blessing.






















