LinkedinLunatics

4211 readers

750 users here now

A place to post ridiculous posts from linkedIn.com

(Full transparency.. a mod for this sub happens to work there.. but that doesn't influence his moderation or laughter at a lot of posts.)

founded 2 years ago

MODERATORS

csm10495@sh.itjust.works

crmsnbleyd@sopuli.xyz

259

Liking any of these indicates a belief system I don't agree with (sopuli.xyz)

submitted 1 week ago by slazer2au@lemmy.world to c/linkedinlunatics@sh.itjust.works

84 comments fedilink hide all child comments

cross-posted from: https://sopuli.xyz/post/24303260

URL: https://www.linkedin.com/posts/michelesollecito_in-my-own-company-i-wouldnt-hire-anyone-activity-7309491565603835904-uBhX

you are viewing a single comment's thread
view the rest of the comments

[–] sugar_in_your_tea@sh.itjust.works 3 points 1 week ago (1 children)

Sounds like you were hurt by an ORM.

One huge benefit of an ORM is that it does type checking. it makes sure your tables exist, relationships are valid, etc, and it makes easy things easy. If you add a column, it'll make sure it gets populated, give you decent error messages, etc.

As long as you use a proper repository pattern setup and isolate DB interactions from the rest of the code, how you construct the queries is completely up to you. I try to use DTOs to communicate w/ the repo layer, so whether an ORM is used or direct SQL queries is largely an implementation detail.

[–] asdfasdfasdf@lemmy.world 2 points 1 week ago (1 children)

https://github.com/launchbadge/sqlx

Not an ORM, but uses Rust's compile time macros so you can write raw SQL and it will type check everything against either a real database connection or a JSON cache of the database's schema.

Absolute best of both worlds.

[–] sugar_in_your_tea@sh.itjust.works 2 points 1 week ago

That sounds really nice, I'll have to check it out.