3
2 Comments

A simple TCP packet started it all

It all began with a simple TCP request.

Some server talked to my server. Somewhere in the cloud.

A timid SYN packet. Almost fearful. Knocking on my server's door.

My server felt encouraged. Powerful.

  • "ACK. "I'm here. What's up?"

The chattered started.

Back and forth. It all went down really fast. The incoming server had a short yet important message to deliver.

The payload was analyzed and redirected to my code.

Something was happening.

Something important.

  • "General, this message comes directly from Stripe."

  • "Wait, are we on dev-mode? staging perhaps?"

  • "No, sir, my ENV variables indicate we are in production. This is a real payload."

  • "For fuck's sake, Lieutenant, why are you dragging your feet on this? Inform our developer in chief! Immediately!"

And so it went.

Cascading effects that resulted in my Telegram app notifying me, while I was having dinner with my wife, two minutes before my 10pm do-not-disturb settings would go into effect.

IMG-E8-C8-CBE97390-1.png

And so it happened; the first paying customer of my journaling SaaS for people who struggle to keep a consistent journaling habit.

Not 24 hours later, before I could even write this very-serious report, a second of our lovely customers upgraded their account, right after that customer sent us a cheerful email, mentioning how they had never gone past a few days of journaling consistently and now they were onto their 12th in a row writing!

😍

PS. This post was brought to you by someone feeling cheerful and silly, but, clearly, with no knowledge whatsoever of military hierarchy. Be kind! :D

on June 5, 2020
  1. 1

    Ha ha great stuff! With WFH I sometimes think “the sum total of my work today was shifting a bunch of TCP packets” no one knows if I’m really here! Spooky. Even the “money” you earned here is just bits! Well done mate..

  2. 1

    Haha! Congrats to you!
    What a nice way of communicating your success!