Mute the ads

Sloppy joes is the new spaghetti code

You can’t reason with an irrational opinion. I applaud you for trying, but don’t blame yourself if it doesn’t work.

Yep I’d say it’s better to find someone you can leave him with while you’re overseas.

He has to create opportunity for foreign actors to funnel money to him.

It’s not illegal to sell a $1,000 watch for $100,000. That way he doesn’t have to actually launder the money.

They can also shoot you if you’re near the person who didn’t pay the $2.90 fare.

Wash their hands after using the bathroom.

WebMD: You have cancer.

Click bait. From an article last year:

These effects may be troublesome, but they are short-lived; re-ionization occurs as soon as the sun comes up again.

https://earthsky.org/todays-image/spacex-launch-punches-a-hole-in-the-ionosphere-red-blob/

I don’t understand how their decision 3 years ago “worked” and that’s why they’re changing the license again.

I remember reading that the banks who loaned him the money haven’t been able to sell off the debt.

* { display: flex; }

Is that your final answer?

1. See GetOffMyLan’s comment. An application will have a finite set of queries it needs to make. Depending on the complexity you may have to enumerate them, but sometimes you can build them up dynamically, or even come up with SQL that will cover multiple cases depending on parameter values.
2. I think GetOffMyLan’s advice applies here too.

When you’re creating a layered architecture you want to limit a lower layer from knowing what’s above it. If you tightly couple your data layer to the view then you lose flexibility. Imagine having to implement some batch processing features that don’t involve the web.

A lot of this is overkill for a small app so if some it seems pointless it may be because there isn’t a team of devs working on the same codebase.

The repository is responsible for talking to the db. Services are where your business logic lives (and ofc there’s always some leakage of logic into the db).

It’s ok for a service to call other services and multiple repositories, but a repository should only talk to the db. It should not call other repositories or anything else.

It’s ok to rely on db constraints for validation checking.

I’m not too familiar with EF specifically, but I’ll give you my general advice:

1. Column filtering can be done in either the repository or service layer.
2. Your transaction should be scoped to the service method. MovieService should call both repositories.
3. Prefer filtering in the repository
4. I don’t know this one

Yeah but where’s your poop knife?

What’s their ticker? I looked up BSOD but that’s not it…

On man that was great.

Seems like overkill when a pit with sharp rusty sticks would work just fine.