While getting data into an S3 bucket from Kafka in AWS seems simplistic with a few clicks, doing the reverse required exploring some alternatives.
That's what I talk about in this recent post.
https://t.co/IHi9eNyN42
Top takeaways from @stanine, COO/CPO at @Rippling:
1. Extraordinary results demand extraordinary efforts. “If you ever find yourself in the comfort zone at work, you’ve definitely made a mistake.”
2. Your job as a leader is to preserve intensity, not buffer it. Every layer of management can dilute the founder’s urgency by an order of magnitude. Don’t protect people from high standards. There’s an infinite supply of people who will advocate for relaxation; don’t be one of them.
3. Never be a “chill boss.” Chill doesn’t accomplish anything. Be intense, be respectful, be good, but don’t be chill. Nobody in a position of leadership actually wants to coast. The invigorating message isn’t “Take it easy”; it’s “Let’s go win.”
4. Understaff every project on purpose. When you have too many people, the lower-priority work gets done. It also creates politics and wasted effort. Deliberately keep teams lean. The wisdom is in knowing when you’ve gone too far.
4. Processes exist to reduce volatility—but they they will suppress creativity. Your payroll system should be boring and predictable (low volatility). Your new product experiments should tolerate chaos (high creativity).
5. The “bored and tired zone” is where great teams separate from good teams. Before you hit an inflection point, the work feels endless and unrewarding. You don’t want to write the documentation, you’re sick of the 19th bug. Push through anyway. That’s when competitors lose.
6. Treat escalations and complaints as gifts. Customers don’t want to bother you. Your reports don't want to bother you. That silence hurts you. The only way to improve is to know the problems. Chase them. Every escalation is data on how to make the system better.
7. You learn far more from success than failure. The “failure is the best teacher” line is comforting but misleading. Matt learned more in seven years at Rippling than nine years at his struggling startup. Join winning teams. Watch how it’s done right.
8. If you’re wondering whether you have product-market fit, you don’t. When it arrives, it’s unmistakable. Matt spent nine years at a startup thinking he “maybe” had it. At Rippling, it’s obvious. That’s what PMF feels like.
9. Quitting is sometimes the smartest move. 4-5 years in without clear traction? Maybe it's time to quit. “Never give up” serves VCs, not founders. Time is the one resource you can’t get back.
10. None of this matters—and that’s liberating. We’re on a blue marble drifting through space. Silicon Valley in 2025 is Florence in the Renaissance: a once-in-history moment. Play the sport with everything you’ve got, but never forget it’s just a sport. That perspective is the backstop that makes the intensity sustainable.
@BisleriZone Your customer care support is horrible. I have been trying to reach out for over 2 weeks! No response to emails, no one answers the phone!
My account is inaccessible and I'm unable to do anything.
Have you considered exploring Rust for performance critical applications? I ran a simple test to demonstrate why it's worth looking it.
https://t.co/o6lzticAn7
"I need to process data streams at scale against some static rules changing overtime. Is there a way?"
Here is a short write-up on processing data streams with rules ingested dynamically using Flink + Serverless.
https://t.co/lzRW1zGJjn
#aws#flink#lambda#kafka#serverless
The incessant follow ups and calls were pointless as the robotic responses from the customer care support led to no resolution or any investigation there of.
Probably the only ever time ever I’ve experienced where customer complaints/resolution isn’t @amazonIN’s top priority!
My sister lost money (3K) for product that was never delivered but was marked delivered at 10:58PM, which is a time at which no one ever delivers!