Anthony Lee

Taking my kids, no doubt!

Not guilty...

I can't express how much I will hate europe if I have to click a button every time I want to refresh a feed.

The printer with the ink tanks instead of cartridges is pretty cool. I'm just not sure how much you can shake it without spilling ink everywhere when you get mad at it.

This bird site is something else. Where else can you just randomly chat with industry leaders?

Aws Pricing Lambda > Fargate > Ec2 But that only applies if you are running it full time. At lower scale, Lambda can be very cost effective. Just watch out for the tipping point!

When building an event-driven architecture, it's important to avoid a common trap - building producers that require knowledge about the needs of consumers. It's okay for a producer to have zero knowledge of what happens after a message is produced. This allows for proper decoupling between systems and enables other teams and/or systems to use the event however they see fit. Remember, publish any data with an event that should not be private. This way, you create actual events instead of issuing commands to consumers. For example, suppose we have a baseball app. We could produce a message each time a batter is out. We could call this message 'batter-struck-out'. We know our Stats consumer will want to know when the batter struck out so we add the batter number in the data for the event. This 'event' could work, but it creates a coupling that makes this event only valuable for the Stats consumer. We are simply issuing a command to our Stats consumer to record the strikeout. Instead, let's back out and record what's actually happening and all of the data we know about it. Instead, let's use the event 'pitch-occurred'. With this event, we'll include everything we know about this pitch. What type of pitch? Who was the batter? Who was the pitcher? Were there any RBIs? Was it a hit or strike? By publishing this event with all of the information we know, we now have an event that can be used by our Stats consumer as well as our Scoreboard, Inning Tracker, and Concession Stand systems to determine when to start shutting down. Our advertisers may want to send fans a promotion when a home run occurs; this same event would work for this purpose. So, next time you create an event, ask yourself: am I creating an actual event, or am I issuing a command? #eventdrivenarchitecture #systemdesign #softwareengineering #kafka

Not sure why @elonmusk allows this type of community note on ads when dropshipping is a legit business. Not a good look for people looking to advertise.

May *cause* a recession. 🤣 My man, we are already in one.