A major cheat code in life: Knowing what you actually value...and trusting yourself long enough to see it through. Time is undefeated. It humbles the arrogant. It reveals true intentions. It rewards the steady. In a world chasing shortcuts, patience is a massive advantage.
In a microservices architecture where services communicate asynchronously through a message broker like Kafka, handling idempotency is critical to prevent issues like duplicate message processing, which can occur due to retries, network failures, or replays.
What strategies would you implement to ensure idempotency in microservices that consume messages from a message broker like Kafka?
Big news — we've partnered with Apple to integrate Tailwind CSS into Safari directly, making it the first browser that can render Tailwind sites with 0kb of CSS over the wire.
Do your part and ship your sites with no CSS file to force other browsers to do the same 🤘🏻
God will sit you down and break you to humble you, then isolate you to build you. Then give you back everything plus more to prove to you he’s real and show you everything happens for a reason.
Please teach your kids about social capital.
About pouring kindness into their friendships and interactions. About building a community around them.
About being resourceful and contributing to the greater good of their circle outside of just family.
Underrated design tip: Just sit and stare. Don’t rush to copy—observe. Notice the spacing, colours, and flow. Let it teach you. Great design whispers; you have to listen.
hot take -
When building an API - never start with the systems architecture.
Start by designing the ideal syntax, and work your way backwards.
DX and consumer ergonomics is the most important thing when it comes to API, library & frameworks design.