You are correct, useEffect can be dangerous if you don't know exactly what you are doing. I would go so far as to say that most people use it incorrectly. This includes myself, I am not great at using React and end up using it in the wrong places, which according to a colleague, it should just be avoided if possible.

They need to start by removing the support structure from the building itself, they should not have a working facility when it is seized.

I used an eGPU for a laptop a couple of years ago. When I started to do testing, I found that thunderbolt only had the bandwidth equivalent of less than 8 lanes of PCIe gen 3. This could not be the case anymore if thunderbolt has a new standard.

I think you mean The Hague, that is where the ICC court is.

It's an inference model. It does not understand code no matter how much context it has. It can however output the most probable solution based on the context it has.

He is not Quebecois, he does not even speak French with a Quebecois accent.

Ai will never grow into a Sr. Software Developer they will just code worse than the worst developer at your company. Unless they magically learn how to design good architecture, they won't replace people in the long term. They are currently just creating more work overall by giving people the ability to create quick and dirty bad code. I inherited a tool vibe coded by a Jr. that will take me twice as long to fix it as it did to for them to make it. I am trying to convince my boss to let me throw it away and start fresh because it will save time but it is a hard sell.

"You know that temp shitty load balancer you wrote on your second month to get things up again. We still use it to this day." My boss last week.

It's funny because once the diamond is on the ring and sold it becomes worthless, the metal in the ring may be worth more than the stones after it leaves the store. I had thousands of dollars worth of diamond jewelry and could barely get a few hundred for it.

One day you will inherit a code base so bad that you'll end up commenting old code just to make sense of it for yourself because nobody in the company has touched in a couple years and the last people that did no longer work there. It will be dangerously coupled, if you make the right change somewhere it will break everything else. It will be true spaghetti code where you spend 30 min just following a code path to figure out what and why an input into a function needs to be what it is to able to come out of another function in an exact format for anything to work.

Your so called comment standards and principals are fine if you are building something from the ground up, but the other 95% of the time, you do what you gotta do because your were blessed with a turd that is impossible to polish.