Shivanand Velmurugan

Give this playlist a listen: Mullard Nights open.spotify.com/playlist/37i9d…

4/Then when you try to uninstall the desktop app, you get this:

3/ They ask you for an exit interview and why you are leaving 3 times (you need to suffer through each of it) (Friction #5)

I unsubscribed today from ChatGPT (yes, for the reasons you are thinking of). It sure was painful. A Thread:

Hello PMs of Vancouver! Here is an opportunity to join the amazing Eventstream team at Microsoft. If you want to know about what we do in this team, or want to dive deeper into my experience joining this team about a year ago, come chat. linkedin.com/posts/vshivana…

DO NOT VIBE CODE A 200,000 LINE SOCKET LIBRARY IN C 😭

Most engineering teams screw up messaging because they don’t understand one thing: Streams hold truth. Queues do work. When you get this wrong, your system bleeds. I’ve seen $10M mistakes from teams who dump everything into queues: “Just push the order to a queue and process it!” Most Queues delete messages after work is done. No history. No replay. No audit. Just pain and guesswork. On the other side, some teams fall in love with Kafka: “We’ll stream EVERYTHING!” Here’s the rule I wish someone told me early: If the event changes the business → Stream If the message is an action to perform → Queue Streams = OrderPlaced, PaymentAuthorized, InventoryReserved These are immutable facts. They must be durable, replayable, ordered, and auditable. Queues = SendEmail, CapturePayment, GenerateInvoice These tasks exist temporarily. They matter NOW, not 6 months from now. Event enters the stream → workers derive jobs → queues execute tasks Ledger first. Assembly line second. Everything else is technical debt disguised as cleverness.

memory

@mazeincoding I’ll do it with one — meeting

scare a developer with two words

@ThePrimeagen Have you tried implementing a discriminated union? C is just *chef’s kiss* for this. No other language makes it simple or easy to this. I spent 5 years building a DSL for a router OS, and C over C++, Java (go and rust didn’t exist then), Lua, precisely for this reason.

i do find it a little offensive that C has a more robust type system than Go

Most engineers learn system design backwards. They jump to Kubernetes before they understand what a network packet even does. Here’s the order that actually makes you dangerous: 1. Networks first HTTP. TCP. DNS. Latency vs throughput. This is the part nobody studies. This is like trying to bench 300lbs without learning to squat. 2. Databases second SQL vs NoSQL, indexes, replication, and partitioning. If you can’t reason about data -> you can’t reason about scale. 3. Caching Redis, CDNs, TTLs, eviction policies. 70% of scaling wins come from avoiding queries. 4. Queues & Streams Kafka, RabbitMQ, SQS. This is how you decouple timelines and handle spikes without blowing up servers. 5. Load Balancing Round robin vs least connections vs consistent hashing. You understand how to scale horizontally without chaos. 6. Build 5 classic designs yourself - URL shortener - Rate limiter - Chat app - Feed system - Notifications 7. Read real-world post-mortems Real learning is failure exposure. You see what broke. You see WHY. You don’t become good at system design by memorizing diagrams. You become good by understanding the physics of distributed systems. Latency. Durability. Throughput. Availability. Cost. Those 5 forces rule everything.

@henrythe9ths FUNDRAISER

I got rejected by 144 investors before raising $150M for my $200M+ rev/year startup. After 144 rejections, I started questioning our approach. Were we solving the right problem? What were we doing wrong? Why weren’t investors seeing what we were seeing? Were we the right team to build this? We tried everything: different pitch angles, new deck structures, and reframing the problem. Then came the 145th meeting, where we closed our first growth round. That yes made everything worth it. But getting there took years of mistakes and hard work. We went through a lot of trial and error just to figure out what resonates with investors. We tried dozens of approaches to figure out what made investors engage. Some landed, most didn't. But each iteration taught us something about what builds conviction versus what just sounds good on paper. And once we cracked that code, our Series C closed faster than expected. And today, I see so many founders in the exact same position I was in 10 years ago: grinding through rejections, questioning everything, and trying to figure out what works. So today I want to give you the resource I wish I had back then: Something that shows you exactly how to structure these conversations and navigate the entire process (because the fundraising cycle can be a big distraction and take a toll on you as a founder). So I've partnered with Notion's Startups Team to create the essential fundraising resource that helps you avoid the mistakes that cost me years. Here's what you are getting: • The actual decks I used to raise $150M for Super[.]com (Series B, C) • 50 real examples from funded startups like Eleven Labs and Artisan AI • A searchable database of 10,000+ investors - angels, VCs, and accelerators you can reach out to immediately (this alone would take months to build manually) • An AI-powered fundraising agent built into Notion with step-by-step prompts (no separate ChatGPT needed) Want access? • Like and share this post • Comment "FUNDRAISE" • Follow me so I can DM you the link I'll send it over ASAP. P.S.: If you are serious about fundraising (now or in the future), you should grab it right away.

@dai_shi @excalidraw This is excellent. 1/ How do I control the order? 2/ How can I control the speed of each group? Most of the time, I want the group to render instantly, like it's one item 3/ Also, how can I make something disappear?

Do you want to create animations with @excalidraw ? Here's what you can do with excalidraw-animate! #json=5648485109989376,gzrPo2btwGzfkclrqgZ4yg" target="_blank" rel="nofollow noopener">dai-shi.github.io/excalidraw-ani… Does anyone have other examples to try?

@ranman Ha. I knew one of those would trigger you sufficiently. 😜

@shiva 6?!?!?!?

Well... may as well go out on a bang... Spaces. No tabs.

@KRollo7461 @austin_rief Not to be pedantic, but that sir, looks suspiciously like an en-dash!

Ehh. Honestly if you write something and an ai polishes it. Its not cheating. Besides i see so many silly people during high level conversations replacing all the emdashes with ";" which is kinda funny. Like clearly you dont usually construct and argument with 4-5 semicolons. So whether or not people are using ai only to write there arguments neater or actively relying on ai to construct whole arguments in either extent the the stigmatisation is real. That why I leave them in. Because my work is good either way. But considering the grammars Nazi wars have come and end after 25 years only due to ai polishing id like to add theres just no fucking pleasing some people so write however the fuck you want Ehh. Honestly, if you write something and an AI polishes it, that’s not cheating — that’s just editing in the 21st century. What cracks me up is seeing people in high-level discussions swapping every em dash for a semicolon, like, mate, nobody naturally writes with five semicolons in a row. Whether you’re using AI to tidy your sentences or to build your whole argument, the stigma’s there either way. That’s why I leave the em dashes in — my work holds up regardless. And honestly, after twenty-five years of grammar-Nazi wars finally dying out thanks to AI editors, it’s clear there’s just no fucking pleasing some people. So write however the fuck you want. "Its not my fault the rest of the world has the brain power of a potato".

You should never use an em dash in your writing anymore. You will 100% be accused of using AI, especially if its on social.

@austin_rief Never shall I be refused the use of the beloved em-dash — we cannot let the heathen take over our rights to a punctuation or two

@QuinnyPig It is cheaper, although I hope they fix it as a consequence of this outage.

Moving all of my Oregon based workloads to us-east-1 today so I don't feel left out for the next major AWS outage.