Matty Stratton

@michaelhedgpeth But still, celebrate that plate! My PR was 5×315lb on Feb 28, 2025, but I’m not anywhere near that after taking over a year off 😂😂😂

@mattstratton You're braver than me nice work! I'm at the one plate level and it takes an act of congress for me to go up

Deadlifted two plates! (Not a PR, but it’s a milestone for this “second time around” lifting)

@michaelhedgpeth I definitely got much better with progression once I moved to a program like GZCLP that’s built for specific progressive overload (especially in a way I don’t have to actually think about!) That said, no program in the world makes my OHP progress when it doesn’t want to lol

Your shell has two audiences now: you, and whatever coding agent is running commands on your behalf. They want very different defaults. Wrote up a tour of my .zshrc, including the AGENT_MODE block that detects which one it's talking to and adjusts accordingly. dev.to/mattstratton/w…

You can follow my progress and journey at mattstratton.com/fitness if you want (or don’t, I’m not the boss of you)

I really wish we’d stop with this advice. The open to work banner doesn’t make you look desperate. It signals that you’re open to work. That’s it. I’ve hired a ton and it’s a convenience. Any recruiter or hiring manager who claims desperation is a cultural red flag.

And I did it!

I convinced myself. Workout started!

Trying to convince myself that I need to work out tonight

@TheNoahHein Like two weeks into joining Chef as a sales engineer I crushed our VP of sales at table shuffleboard and that might not have been my smartest move When I started this tweet I was remembering that it was Galaga, which made it a more on topic story

I think the most career cred I ever got was I joined a company, and we had an offsite 1 week in where I beat the CEO in a smash bros tournament. Gotta crush the competition

These past few weeks at @EntireHQ have been so exciting. We just launched our git hosting platform, and the reaction from the community has been incredible. People are genuinely embracing our product and our vision. But I’ve also seen some completely fair curiosity. Some people are wondering: why is everyone trying to rebuild GitHub? GitHub has done the job for almost two decades. It also has established alternatives like GitLab and Bitbucket, and there is a new wave of git hosting. But now there's this new wave of git hosting competitors popping up like Tangled, Cursor Origin, gitlawb, and most importantly Entire. To understand why there is a sudden race to rebuild git hosting, and why Entire’s approach is the one that will actually last, we have to look at how git hosting works under the hood. Read my article to learn how agents have impacted the git hosting experience, and how Entire is solving it.

Aggregate is coming. The premiere event for people building with time-series data and Postgres. 📍 New York City + Livestream 🗓️ October 6, 2026 Register now: tsdb.co/agg-x #TimescaleDB #Postgres #TimeSeriesDatabase #Aggregate2026 #TigerData

Twenty years of posts, 2,630 of them, moved into one monorepo with full git history intact. This dev shares the stack and the weird bugs. { author: @mattstratton } dev.to/mattstratton/i…

Moved the heavy circles today !

Maybe eat something first though

Okay Matty, enough playing around with computers and your website. Go lift some weights

@Thom_K_NL @wongmjane Well to be fair my solution for this is adapted from that blog post. It's done a little bit more at the command line, which I talk about in my other blog post about my dot files and my zshrc dev.to/mattstratton/w…

@Thom_K_NL @wongmjane I’ve been using this solution for years :) netmeister.org/blog/keychain-…

How do y’all keep your dotfiles in sync and system up to date across multiple Macs / computers?

Spent my day off work merging my blog, speaking site, and @ThePracticalDev sync tool into one monorepo. preserved 2,630 posts back to 2001, byte-for-byte URLs, real git history via subtree (not squashed). also discovered Ruby’s YAML parser will silently turn your unquoted timestamp into a Time object and then refuse to load it. love that for me. full tour: mattstratton.com/writing/mattst…

Continuous aggregates are one of the most popular TimescaleDB features: incrementally maintained rollups that accelerate analytical queries while transparently handling late-arriving and backfilled data. The challenge is that analytical questions evolve. Need another aggregation? Historically, that meant dropping and rebuilding the continuous aggregate. In @TimescaleDB 2.28, adding a new aggregate to an existing continuous aggregate is just: > ALTER MATERIALIZED VIEW ... ADD COLUMN New values are computed automatically going forward. If you want historical values for the new column, simply run a refresh. Analytical requirements change. Your rollups should be able to change with them.