PWV Portfolio Feed

it's in downtown brooklyn, three blocks away from a police station, which is what i guess… kind of… explains it. a few weeks ago they had a dog sitting in the window, dyed blue

reporting from the redpilled blue lives matter dog grooming command center

My wishes for #WWDC:
- Deprecation of Package.swift and .xcodeproj in favor of a unified graph language.
- Content Addressable Store (CAS). There are already foundational work in the swift-build repo.

👉 Custom page builder lets TKstairs create unique layouts for every section
👉 Easy product publishing to Google Merchant Centre
👉 Case studies, blogs, and product information managed directly through Directus
👉 Consistent brand experience across all custom configurations

The line between the compiler is helping ensure the code does what is supposed to do and I’m adjusting my code to please the compiler is a fine one to walk.

💡 Schema changes don’t have to be scary.

If this helped, share it with your team, or keep it handy for when you’re staring down your next big migration.

Bookmark this for later! 🔖

Step 2️⃣: Contract

Once your app fully switches to firstName and lastName, drop the old name field.

🙌 Migration complete. No downtime, no stress.

Step 1️⃣: Expand

You add new fields (firstName, lastName) while keeping the old one (name).

Then, write a sync trigger or job to keep data in sync.

✅ Nothing breaks. Reads/writes continue as usual.

Use the Expand and Contract pattern to migrate schema changes without downtime.

1. Expand the schema
2. Backfill the data
3. Migrate the app
4. Contract the old field

🎉 This keeps your system live the entire time.

😱 Migrating database schemas can spiral into downtime.

Downtime = lost revenue, unhappy users, midnight deploys.

Want to avoid it completely?

Here's a proven pattern to ship schema changes safely in a team👇

That’s a model I’m pondering for @tuistdev. You bring your API keys, and we take care of the rest plugging the hosts to GitHub or GitLab. The costs are mostly on you, and you pay a flat fee for our managing of the those hosts.

They resort to automation tools like Ansible, but I think it’d be amazing if they could do everything through a UI that allows them to add Mac Minis to their own pool, and let a tool provision them automatically.

I’ve already come across a a handful of companies that set up their own Mac infra to escape abusive pricing models by some CI providers 😅.

And I’m here for it.

With the launch of Chai, we have seen tens of thousands of new AI agents being vibe-coded both by builders and expert developers. 

Everyone is seeing a huge productivity gain here. From builders to developers to product managers everyone is building agents like never before.

There’s a huge amount of grey area between what’s vibe-coded and what’s AI-assisted coding. Do both. 

Both btw are much better than the drag-and-drop BS no code and low code alternatives.

It’s like when Tailwind first came out, as someone who always wrote CSS from scratch it took me a while to see how Tailwind was not a framework but like an API for CSS. 

I think we are in that phase of vibe coding where a lot of people judge it by the cover.

Vibe coding is going to replace every no-code low-code alternative. For good reason as well. And I would never understand the hate vibe coding gets. 

The AI-assisted coding and vibe coding are not far too different. I’m a convert tbh.

📦 ~3,243,043 downloads this week.

Thank you 💙