It actually makes sense that code is becoming amorphous and we will no longer scale in terms of building out new features (which has become cheap), but by defining stricter and stricter behavior constraints and structural invariants.

Yeah, "what you're able to build" is no longer one of the most important things, "what you won't build" just became a lot more important.

With AI, the onus is entirely on you to prompt the AI to perform an ethical practice interview and avoid gaining an unethical advantage by having AI make up answers for you.

It just makes me wonder about the importance that an understanding and commitment to ethics will play as people start to use AI more and more in their daily life.

They definitely make line that is strong enough but it's thicker and fish that spot it are hesitant to take the bait. So there's a balance: strong enough not to lose fish but thin enough to gain an edge over the other competitors.

I was thinking about designing a line that thickened and strengthened in response to the tension of reeling, but that I realized a negative poisson ratio was the opposite of what I wanted.

How many kids do you have, dad engineer?

They should probably replace that with 2 if statements to make the error path and the non-error path obvious:

    if err != nil {
        return nil, err
    }
    if match {
        return rule, nil
    }

Perhaps they plan to lay off a lot more of those employees in the next round and they want to get the process figured out early?

or they use the restructuring as a valid reason to do a layoff and get rid of "dead weight"

- generate code from running database and use a type-safe query builder (https://github.com/bokwoon95/go-structured-query)

Interesting. I've been looking at https://github.com/bokwoon95/go-structured-query but I'll have to look at reform too, now. Thanks.

Reform documentation isn't always that good but the implementation and generated code is not too difficult to read when trying to understand how everything works.

Thanks for sharing go-structured-query, I didn't know about it.

Correct me if I'm wrong, but isn't some of the Parler violent content and speech that violated the TOS still on Twitter in the form of screenshots? Or have there been efforts by big tech to remove them too?

I'm sure some of it is in the form of screenshots. But Amazon's court filing shows plenty that is in plain text.

https://deadline.com/2021/01/amazon-court-filing-parler-for-...

If Amazon can find it and has identified it, why won't Parler remove it?

Signed, Lorenzo Anderson

At the very least, every company hosted on AWS should be evaluating whether they are liberal enough to stay in Amazon's good graces.