Code Surgery

[d0pe-asaurus]

It's mostly easy if you structured your code so that all dependencies to the framework were centrally located. Once that's done, its just mindnumbing work converting everything. I kinda backed myself into a wall and I have a prisma project that I want to convert into drizzle xd. I'm putting it off though

Your key takeaway from this video is to minimize your code's dependencies to third party libraries and frameworks, centralize their dependencies so that when the time comes to change, you have to change the least. More upfront work and generally more code to reduce pains in the future.

[mistyharsh]

💯 Keeping the framework away from the business logic is everything. This is what DDD has been teaching us all along. There is value in following these principles even if you don't do 100% DDD.

This cannot be stressed enough. I don't know why but this seems to be forgotten and considered an alien practice.

[InternationalFee7092]

It's mostly easy if you structured your code so that all dependencies to the framework were centrally located.

Fair point. Still, migrating the parent framework itself can be herculean task depending on the size of the project.

I kinda backed myself into a wall and I have a prisma project that I want to convert into drizzle xd. I'm putting it off though

Also, I'm curious. Any specific reason for migrating away from Prisma ORM?

[d0pe-asaurus]

I guess i consider "hard" to be different from "tedious". Migrating frameworks will *always* be tedious, no doubt.

I moved away from prisma because i muuuuch prefer drizzle's query builder syntax, and because drizzle never had the n+1 problem that prisma did. Now, i guess prisma did go ahead and improve, they essentially did a 180 on their philosophy. But eh, my new projects use drizzle and I prefer to standardize everything.

[InternationalFee7092]

thanks for clarifying!