Regardless of the type of pan you are using, you will find eggs ate much less likely to stick if you wait for the pan to be hot before you out the eggs in. I don’t know why this is, but if you put cold eggs in a cold pan, they will stick when you cook them.

I’ve seen several very sympathetic posts on LinkedIn, including one that called him out as a hero and role model for coming from a small town and rising to the top of US society.

Good point. I think knowing where to draw that line comes with experience (and having to fix lots of other people’s code).

I would have liked some comments explaining the rules we are trying to enforce or a link to the product requirements for it. Changing the rules requirements is the most likely reason this code will ever be looked at again. The easier you can make it for someone to change them the better. Another reason to need to touch the code is if the user model changes. I suppose we might also want a different password hash or to store the password separately even a different outcome if the validation fails. Or maybe have different ruled for different user types. When building a function like this I think less about “ideals” and more about why someone might need to change what I just did and how can I make it easier for them.

Gen AI is like super-autocorrector.

Sometimes after upgrades, even minor ones, I find it useful to run analyze on all of the tables. I usually do analyze verbose; so I can see which tables are getting analyzed. This will assess every table so the query planner can make better decisions about how to resolve queries. If the query planner is making bad decisions I/O and CPU will be high and query performance will be poor.