Welcome to my PinkLetter. A short, weekly, technology-agnostic, and pink newsletter where we cultivate timeless skills in web development.
You take the blue pill—the story ends, you wake up in your bed and believe whatever you want to believe. You take the red pill—you stay in Wonderland, and I show you how deep the rabbit hole goes. Remember: all I’m offering is the truth. Nothing more.
So, what do you do?
Better said, what impact do you enable?
Grueling questions. Really.
I’m not surprised most of us end up taking the blue pill and stop looking for answers.
But, some of us, cannot help but think about that damn red pill. And if that’s you, let me propose an exercise.
Create a landing page with your offer and ask (potential customers) to buy your services/products.
Remember, it’s not about you, it’s about the change you can enable for your clients.
Here’s what my fullstack web development agency would offer.
Reply to this email and roast me.
Static types are not about “classifying the world” or pinning down the structure of every value in a system. The reality is that static type systems allow specifying exactly how much a component needs to know about the structure of its inputs, and conversely, how much it doesn’t. Indeed, in practice static type systems excel at processing data with only a partially-known structure, as they can be used to ensure application logic doesn’t accidentally assume too much.
(Riccardo: Before I met Elm, I had the same objections against static types.)
A demo of using Dark to build an office sign in application (API, data storage, external API connections and background workers).
(Riccardo: When Smalltalk meets Dark magic.)
(Riccardo: Some (not all) solutions are better encoded in declarative SQL than JS.)