When's the last time your first project in a new technology was also your favorite? Doesn't happen very often ...🤔
It happened to me in November 2018.
Pat Walls of Starter Story fame posed a challenge: Build a startup in 24 hours.
Absolute mad man. There's no way.
Is there ... what if? No, no that's crazy. But maybe ... no hell no. Unless ...
I have been paying someone \\$500/mo to do a boring task 👉 take my markdown, put images on imgur, screenshot tweets, code snippets, and youtube embeds, export to HTML and paste into a newsletter.
That sounds automatable ...
Fuck it, Pat Walls you're on!
12 hours later, TechLetter.App was born. You see its output every time you read my email.
And every day it feels like magic. 🧙♂️
Write email in markdown. Paste into box on the left, get rendered HTML on the right. Basic markdown parsing and rendering. There's libraries for that.
Here's where it gets cool 👇
TechLetter.App uses an AWS Lambda to spin up a Chrome browser and take screenshots. Tweets, Youtube thumbnails, Instagram, code snippets, CodeSandbox, and a few more.
Think about it – every time you paste a link, a few dozen steps go just right in a dance of magic:
- Markdown plugin recognizes a link
- Matches link to Regex of screenshottable stuffs
- Renders a
<Screenshot >React component
- Component uses
useEffectto make an API request
- DNS config maps request to my API Gateway
- API Gateway says "Oh, _that lambda"_
- AWS Lambda spins up a whole new server
- Function starts a Chrome browser
- Browser loads the link (another magical dance)
- Tells browser to take a screenshot of that node
- Uploads screenshot to S3 as a file
- Returns the URL as an API response
<Screenshot>component renders image
All this in 3 seconds for \\$0. 😳
The future boggles the mind my friend. You can try it at this URL 👉 link to my AWS Lambda
Before you ask: Yes, a lot has happened to this Lambda over the years. Fixes to how Chrome works, tweaks to screenshots, new features, cleaned up the codebase recently. It's been a fun project.
Even got 91 stars on GitHub despite being hardcoded for my usecase and with a Readme so out of date it's hilarious. I should fix that 😅
Sometimes you love things just because they're cool. You don't need an excuse to be a nerd.
And it's saved me countless hours and almost \\$10,000 in outsourcing cost. So that's nice. 😇
Not bad for a few hours of hacking and \\$0 in hosting cost huh?
What would you build, if running server code was a breeze? Hit reply
PPS: the distributed serverless data processing pipeline chomping through millions of events per day that I built at work sounds impressive on a resume, but it isn't cool
Here's how it works 👇
Then get thoughtful letters 💌 on mindsets, tactics, and technical skills for your career.
"Man, love your simple writing! Yours is the only email I open from marketers and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Ready to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz components your whole team can understand with React for Data Visualization
Curious about Serverless and the modern backend? Check out Serverless Handbook, modern backend for the frontend engineer.
Ready to learn how it all fits together and build a modern webapp from scratch? Learn how to launch a webapp and make your first 💰 on the side with ServerlessReact.Dev
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️