Spent most of the day hunting a performance issue with Node.js on AWS lambda, found it, and fixed it. Execution time. Before: 1s, after: 150ms To track and optimize such performance issues, read this quick debugging-horror-story-with-happy-ending thread 🧵

A fantastic visual for debugging Kubernetes apps 🤩by LearnKube learnk8s.io/troubleshootin…

Many questions on #Akka's new license and what it means for #ApacheFlink, which internally uses Akka for cluster coordination. TL;DR: * #Flink's license will ofc not change. * We'll not use Akka 2.7+. * We'll make sure users are not affected. More: flink.apache.org/news/2022/09/0…

This is bad advice. Even with MySQL v8 STRICT mode, there are still a lot quirky things with their SQL dialect. I started with MySQL v3.23 (MyISAM) back in high school and it took me a long time to remove muscle memory I built up with bad SQL habits. Always start with Postgres.

🤯🤯🤯 Entire facebook onboarding Automated with Maestro - from scratch - in 15 minutes: 📽️ by Manish Verma

Took me 17 years of struggle, but I can finally explain cohesion in software design. I dropped the Cohesion chapter of the #TidyFirst book yesterday. I'll summarize here. tidyfirst.substack.com/p/cohesion #payWall

Cohesion: * Things that have to change together *are* together. * Things that don't have to change together are apart. Where? That's for you to figure out, designer. But likely with the things that have to change at the same time.

Figuring out what index to add is challenging (shown to be NP-Hard). But more often we see databases that have too many indexes. This is why we added support for automatically identifying bad indexes in OtterTune for #Postgres/#MySQL last summer: docs.ottertune.com/info/dashboard…

engraved.blog/building-a-vir…

ottertune.com/blog/2022-data…

Excited to share our published paper at USENIX ATC 23 on how distributed transactions were implemented in DynamoDB using a timestamp ordering protocol without sacrificing high scalability, high availability, and predictable performance at scale usenix.org/system/files/a…

DynamoDB internals summary engineering.cred.club/dynamodb-inter…

How to efficiently query multidimensional data on DynamoDB using z-order indexing (lat/long distance, time range overlapping, ...) aws.amazon.com/blogs/database…

Payment websites often disable paste on form inputs They think you're too stupid to copy the right account/routing numbers Refuse to be a victim. Run this code in the console to take the power back

This year's project for our Dist. Sys. course at FEUP will focus on building a local-first shopping list design. I am looking forward to seeing the designs our students will create in the coming weeks.

I have written over 800 technical articles in the last 14 years and they have been read millions of times. I see a lot of folks making the same mistakes I did early on in my journey. So here are some principles to help you get better at writing. 🧵

Ran into a few DynamoDB customers lately concerned about the time it takes to scan tables/GSI's when they need to update schema. We always discuss how much easier this is with range updates in MongoDB, but I also mention the customer guidance I gave back at AWS which is to

“The abstractions save us time working, but they don’t save us time learning.” The Law of Leaky Abstractions strikes again. Every time you use AI, you sacrifice learning for productivity.

AI can write code fast, but it can’t guarantee clarity, correctness, or maintainability. In the age of AI-assisted coding, code quality matters more than ever. Here’s why good code is still the foundation of great software 👇 thoughtworks.com/insights/blog/…