Loading video...
Video Failed to Load
if you’re a react dev but the project uses vue, use vue if it’s an app using inertia, don’t introduce livewire if they use enums for statuses, don’t use strings if the team uses the actions pattern, follow it consistency > personal preferences
38,043 views • 1 year ago •via X (Twitter)
11 Comments

Agree, but, it's easy to get stuck in a pattern that's not so well thought out. I will say: follow the current standards in new code and gradually refactor and migrate old code over time.

🚨BREAKING: Defi App beta is live Crypto's first all-in-one SuperApp is here: - Instantly buy any token on any chain - 10x long memes & majors - No gas, no bridges, no KYC - AI Trading Agents - Self-custody Sign-up on First 1,000 users heavily rewarded

I actually like mixing Livewire (as in Filament admin panels) and Inertia (for the frontend) in my apps. Wouldn’t use them both in the same place, tho.

but ....

This is so incredibly important. And if you have to introduce a new way of doing something, then the whole application should be updated to follow suit. Otherwise fragmentation occurres and the problem gets immensely worse

But if that person leaves. You're the master of your own possible demise.

👍 agree.

There’s an exception to that rule: if the project uses PHPUnit, you do a drift 😉

consistency maintains the status quo. If the codebase is a dumpster fire then consistency means it will never improve

instructions unclear im now using string backed enums

How about my consistent preferences 😜
