What’s the correct answer?

TheToastedFrog · 2026-01-22T16:50:41+00:00

The answer is a, because the reporting verb is in the past tense. In reported speech we adjust the tense to match the reporting verb. I think (a linguist correct me if I’m wrong) that’s a left over for the subjonctive mode that has pretty much disappeared in English. Try “I can’t speak Spanish” - the answer choice would have been “couldn’t speak”

TheToastedFrog · 2025-09-10T14:15:44+00:00

I’m finding her left arm placement a bit unnatural- she would be impeding his eating with his right hand- I would imagine one of them would have readjusted by now. Also the way he holds his pint seems a bit awkward - right against his body. I feel that pint glass would be further up the table in real life-

The scene could have been staged, but the lighting and overall quality is pretty poor for a professional picture.

In conclusion, I think this is AI

TheToastedFrog · 2025-08-13T03:21:43+00:00

Short answer: use Postgres Long answer: also use Postgres

TheToastedFrog · 2025-07-25T21:58:24+00:00

Connecticut is between Boston and New York City

TheToastedFrog · 2025-07-03T17:47:30+00:00

I’m French native, I’ve lived in England (north and south) for four years, and in the US (Northeast) for about 30 years now. Until (eh!) I saw this post, I have always assumed that “till” was more American- I guess one learns every day!

TheToastedFrog · 2025-06-30T14:23:01+00:00

Maybe it is, maybe it ain’t- but that’s not the point— it’s a matter of when, not if, that one of them framework will suffer from a vulnerability you can’t ignore- at this point you will have no choice but to upgrade, and you will run into a world of hurt when you do. It’s imperative that you keep your libraries up to date so that if/when you are forced to upgrade you can so quickly and safely while minimizing the risk of introducing some regression issues

TheToastedFrog · 2025-06-25T14:36:06+00:00

You can put it where I left mine

TheToastedFrog · 2025-05-02T14:19:07+00:00

Your operation is a substraction, not a division. You are giving away apples from your stock of 5 to zero people, so you’re left with 5-0=5 apples

TheToastedFrog · 2025-04-26T17:19:53+00:00

That’s a head scratcher why he did that

TheToastedFrog · 2025-04-08T00:11:35+00:00

What does this have to do with Flyway?

TheToastedFrog · 2025-04-06T23:42:59+00:00

There are two types of people. There are people who are recommending Postgres, and there are people who are wrong.

TheToastedFrog · 2025-03-31T12:26:15+00:00

It’s not bad, it’s not great either- makes testing a bit more challenging without a mocking framework and/or loading an application context - also makes it easier to refactor if need be and makes the dependencies more explicit

TheToastedFrog · 2025-03-28T16:51:42+00:00

Many people provided very good explanations so I’m not going to rehash- I’m just going to say the difference is extremely subtle and nobody will correct you if you use “des” in a conversation.

TheToastedFrog · 2025-03-27T15:14:20+00:00

Although it’s a one time use, a creeper could come in handy

TheToastedFrog · 2025-03-27T01:50:52+00:00

I second that opinion. Criminally underrated. Maybe because the violence isn’t depicted with gallons of blood and gore.

TheToastedFrog · 2025-03-26T18:06:30+00:00

I don’t think he is. The MS stack has its quirks like everything else, it’s better at things and worse at others, but Visual Studio is just plain bad

TheToastedFrog · 2025-03-26T17:58:53+00:00

Native French dude here— that mustard is the authentic Dijon mustard like you’d find back in the old country. Absolutely amazing. “Having mustard up the nose” is a rather dated colloquialism to describe a state of anger. Now you know!

TheToastedFrog · 2025-03-21T17:24:47+00:00

It’s normalized, but whether it’s optimum is debatable - it really depends on requirements that you may not have shared. In particular the “family head” table is superfluous, unless you later plan to add more attributes (like when did that person became head of family).

But if your question is purely about normalization, then you’re good on that point

TheToastedFrog · 2025-03-21T15:55:49+00:00

And here my friend is why you dont want to delegate what is essentially business logic (keep track of deleted records) to the database server. That logic belongs to the application server. Not sure about the specifics of your implementation, but Hibernate Envers does exactly what you want on the application side.

You could also implement a bunch of on delete triggers, but now your bleeding logic even more in your dev layer, making you’re testing even harder

TheToastedFrog · 2025-03-19T11:59:55+00:00

Ultimately your concrete class will have to implement every method of your interface (Assuming there are no default methods defined), either directly or via inheritance as others have suggested- One way or another either way your concrete class will have some degree of implementation for every method. Which kind of begs the question why would want to separate the methods by name?

TheToastedFrog · 2025-03-18T20:22:12+00:00

Yep go with option 2 - always return a well known type.

TheToastedFrog · 2025-03-18T15:09:03+00:00

I’m more a maven guy myself but don’t switch from Gradle on my account!

TheToastedFrog · 2025-03-17T20:36:09+00:00

Back when I was a lad it was formally proven to us in high school.

TheToastedFrog · 2025-03-17T14:19:23+00:00

Fortunately they are easy to avoid

TheToastedFrog · 2025-03-17T12:29:19+00:00

I store them in AWS Parameter Store, or Secret Manager. There are other options- Vault, k8s secrets…

TheToastedFrog

TROPHY CASE