The same way that students are taught to calculate what their theoretical yield should be in chemistry, CS students should be taught te calculato the theoretical number of cycles any particular operation needs to perform, and then treat getting close to that as seriously as chemists do. Sometimes your performance will be low because of all the incidental crap you have to take care of. But for a lot of things we do on computers there just isn't any excuse.

Not bad Graham crackers. Didn't flatten the first batch flat enough, little soft and cookie-like.

My boss is adding me to meetings instead of a coworker. Apparently I'm on his mind. Good or bad?

Nooooooooooooooooo!

I want to see an AI Amelia singing "Poor Wandering One"

We know that emp guns exist. They're walking around Europe pretending they can down quadcopters with them. Get ice some of those so you can kill the ecu of anyone misusing cars. And then let me get one so I can kill the teenager's car across the street when they drive up and leave the music on for an hour at 2am.

What do you mean alembic won't drop enums from a postgres when you run a downgrade. It creates the enums just fine in an upgrade. Now my database is in an unknown state inbetween two supposedly known and defined states. That's your one purpose is to prevent that. And if I would have just written my own sql migrations I wouldn't have this problem, but you sold me on the idea that this was solved. Asshole project.