I was gonna say "may as well be ads", but then 1 literally is 😅

Amazing that hot garbage like that always makes it through

Yeah definitely learned that one the hard way 😅

Ok, my actual stance on that is, if your GitHub lawn is "green", sure, go for it. Otherwise look elsewhere.

Good signal for who not to apply to...?

A+ dad humor

And then in some places, Pennant feature checks would be run and stop migrations from running since the features table didn't exist yet.

Specifically, if I was trying to update a migration for a brand data structure that hadn't been deployed yet, I would just edit the new migration instead of creating another migration to modify the table or columns.

This would require rolling back or wiping the DB first though.

Wait, but if features are stored in the DB, will this break migrations if someone clones the project for the first time? (checking a Pennant feature I mean)

I've had that happen a lot.

Outside-in is always nice.

Works the same with frontend: how do you want your users to actually use it? And you can use a dummy layer for data/content below the layer you're actually working on until you have it all wired up.

Rhys being Rhys 😅

Wait, why subscription hacked?

Also first time trying Blueprint by Laravel Shift. Didn't realize how helpful it would be, especially since I was already in the habit of writing data structure I'm thinking about almost in the format of their Draft file format.

Gonna have to keep using that. 🙂

It's nothing glamorous at the moment, just a personal freelance jobs DB basically—jobs + status + location, orgs they're for, contacts, notes...

It has another supporting purpose that I have to figure out (if it turns out it's even possible). We'll see.

Welcome to the open road! 🫡