Cotton Lane: because this used to be cotton fields, one of the major agriculture crops of Arizona

Prison: because when this prison was built, it was like 25 miles west of town, now it’s continuous city well past this point

Surprise: a western suburb of Phoenix

Zoo: wildlife world zoo, a private zoo with too small cages and little in the way of habitat for the animals.

Trailers: because the Phoenix area is a trailer park that somehow grew up into a city.

It looks like a partially disassembled head band from some cheap gaming headphones. Image searches won’t find it because the metal shouldn’t be visible in the actual product.

You just don’t get 11 dimensional particle physics. I was actually into it up until that point. As soon as they pulled that shit, I would have quit but wanted to finish for our book club discussion.

People forget that there’s already a breakdown of the US between the country and state levels. The federal district courts divide the country into 11 districts. This effectively means there are groups of states where court precedence equates to different interpretations on the same laws.

So if something were to divide the country this map might make a good breakdown. It’s not very geographically regional, but few state borders are.

The various versions of paint it black are fucking fantastic.

First of all, lack of ORM isn’t bad. It’s not a good or bad thing to use them out not use them. What’s bad is not sanitizing your query inputs and you don’t need an ORM to do that.

I think the worst thing I’ve seen is previous devs not realize there’s a cost to opening a DB connection. Especially back when DBs were on spinning rust. So the report page that ran one query to get the all the items to report on, then for each row ran another individual query to get that row’s details was probably one of the slowest reports I’ve ever seen. Every DB round trip was at minimum 0.1 seconds just to open the connection, run the query, send back the data, then close the connection. So 10 rows per second could be returned. Thousands of rows per page has people waiting several minutes, and tying up our app server. A quick refactor to run 2 queries instead of hundreds to thousands and I was a hero for 10 min till everyone forgot how bad it was before I fixed it.