acimim_ha

If I won't do it, somebody else will. And we're back and square one.

Correctness and robustness are not always the requirement. Sometimes it's simplicity. Sometimes it's time-to-market. Sometimes you get fed a broken XML and regex actually does a better job.

I've also been a junior developer and thought that my code has to be correct, look correct and perform correctly. Then I got a boss. Boy I was wrong.

> Case 2. Misuse of IF [NOT] EXISTS

The article doesn't provide any good example of misuse. And that's exactly how you use it. It's clean and simple, no hidden pitfalls. Schema migration tools are overhead when you have a few tables.

and we got "IS [NOT] DISTINCT FROM" in the meantime, for better or worse

"SELECT * INTO table" is not ANSI standard.

Negative publicity is reflected on their equity evaluation. They have great incentives. The system works.

I think with 100 deaths the company would get liquidated. This incident alone probably caused more damage than a cost of one single driver's license suspension.

The topic would not gather nearly as much attention. Why?

I sure did. And I sure did even bigger screwups while driving.

> locations on the moon where conditions are ideal for the study of the early universe.

Doesn't get me particularly excited personally. Scientists should be aware other people have different interests. I want a futurama lunapark.

In the end, government is going to decide. After some war/conflicts. Just like on Earth.

How? Except it would finish sooner. The is no behavior.

I don't really see why:

  public class TestJIT {
    public static void main(String[] args) {
        for (int i = 0; i < 20_000; i++) {
            payload();
        }
    }

    public static int payload(int a, int b) {
        return a + b;
    }
  }

shouldn't be optimized into a 'no-op'. The end-effect is the same.

You missed the important part: they charge for a yearly subscription to their service.