wife and i started wearing continuous glucose monitors a couple weeks ago just to learn more about our metabolic health and we've both learned so much!

going to share the most basic takeaways and then get more and more specific

most basic:
- eat less
- move more more specifically, eat smaller meals and move immediately after

anytime i eat a meal i would have called "normal" sized before, i'm in for a big spike

if i sit after a meal (usually at my desk for work), that spike is exacerbated (and the insulin dump is going to be intense)

😱 omg, next 14 leak!
don't ask how i got these details:

Next.js 14

◆ `site` directory w/ opt-in RSCs ("use server")
◆ AI powered router (GPT-4)
◆ Turbopack now in Beta*
◆ Turboformat (Rome Tools acquisition)
◆ `next/favicon`
◆ `next/centered` "Next.js 14 (very stable) ushers in a new era of computing, transcending the boundaries of space and time, and empowering you to create the unimaginable."

(Mostly moderately successful e-commerce sites, though.)

Stop reading and engaging with threads, a thread Stop

We did it fam. Connecting to @planetscaledata's new HTTP API through an AppSync VTL resolver and fetching data. Pretty excited about this!

(Ignore all of the red flags. I know we'd need to fetch the auth token from secretsmanager just didn't want to make a pipeline resolver yet) Why is this cool? No runtime compute! No lambda function which means no cold start, no code rot, etc. Basically no maintenance at all!

I do this all the time with DynamoDB, but to have a SQL offering that works with this approach is pretty great.

I don’t like to be negative. It’s a lot more fun to only ever be positive and ignore the stuff that bothers you.

But, lack of accountability on the internet is a problem, and the last few months have brought that to a head for me, personally.

Story time: I hang out on Twitter, almost exclusively. I’m mostly interacting with the AWS community here, but also broader tech twitter, and the indie hacking crowd.

Like everyone else, I see the 37293746 (info) products and services hawked on this platform; I also hawk my own on occasion.

I love the DynamoDB API. You can look at any operation and be certain of the performance characteristics.

Contrast that with a SQL query (or ORM operation) where you have to have a lot of context to understand whether a table scan will be needed, etc. This is a huge difference over time. If you’ve built any non-trivial app and maintained it over a year+, you know the pain of troubleshooting poorly performing SQL queries and dissecting query plans.

I get that DynamoDB has a learning curve, but so does SQL (esp indexes)!

Hi aspiring cloud professional, my name is Adam and I need you to listen to me.

First, I make a zillion-ish dollars per year freelancing and I stand to gain nothing from your attention.

I’m writing to you because it occurs to me that things I think are obvious probably aren’t. Like, for instance, the fact that focusing on serverless tech narrows the set of things you need to learn by a lot, accelerating your path to shipping real stuff of value.

No Linux knowledge? Don’t need it! Where we’re going, we won’t need (to worry about) servers.

I turn 35 years old on Friday, which is significant because it's divisible by 5!

To celebrate, here's a list of my 35 favorite AWS services. 🥳

As Mario would say, "Here we gooooo!" 35. AWS Snow Family

This family of services consists of Snowcone, Snowball, and Snowmobile, and I've never used any of them. 🤠

But, how could I not include a service that allows you to send 100 PB of data to S3 on a semi-truck?!

Narrator: he could not, not.

I built a startup on AWS and have advised dozens of startups doing the same.

This is a practical thread with advice I wish I'd been given early in my startup journey. "😩 But, MVP and market fit and AWS-is-too-complex-for-early-stage-startups and you-should-Heroku and..."

Yeah, this thread isn't for you. 😅

This thread is aimed at folks who are already convinced that building on AWS is best for their startup.

AWS is a fantastic way to host your web projects, but it can be intimidating if you're accustomed to the simplicity of Netlify and Vercel.

Why bother with AWS?

There are a few reasons:

💰 Cost efficiency
🎯 Greater control
⚡ Higher performance ceiling

A (practical) thread. While AWS is made up of an overwhelming number of services (200+), you only need to dive into a few of those services to effectively host your web sites and apps.

In this thread, I'll cover three of those services: S3, Route53, and CloudFront.

Earlier this year, I prepared for and passed 12 AWS certification exams.

This thread is an attempt to distill my learnings into a practical guide for others that are pursuing AWS certs. If you're more of an auditory learner, I recently presented much of this information to my local AWS User Group.

You can watch the talk on YouTube (~1 hour):

I'll earn more than $500K freelancing this year, and 90% of that will be through AWS IQ.

There's a super clear path to >$200K/yr as a freelancer if you're:

1. US-based (AWS IQ req)
2. enthusiastic about AWS
3. comfortable (/good at) selling yourself to customers

That path is: 1. Earn all 11 AWS certs

This will cost you ~$1500 in exam fees and prep materials.

Whether you believe in IT certs in the real world or not, on AWS IQ they're a cheat code. AWS certs are featured prominently on the service, and customers will choose you for this reason alone.