I'm in a few women in tech groups. A woman, who is a highly experienced developer, shared that she had a conversation with her male friend, who is a startup founder. He said that his criteria for recruitment are high levels of math and physics since high school and early interest in programming (e.g. age of 10). She said his criteria made her sad and excluded.

A fellow woman developer commented that it's reasonable to feel sad when you learn your good friend is an idiot. I snorted some Monster out of my nose reading this and I'm still coughing and chuckling.

To be honest, the founder's requirements do sound super ridiculous, and I imagine his startup is made up of clones of the same guy type, wearing different shades of gray t shirts and sandals with socks.

My God is map development insane. I had no idea.

For starters did you know there are a hundred different satellite map providers?

Just kidding, it's more than that.

Second there appears to be tens of thousands of people whos *entire* job is either analyzing map data, or making maps.
Hell this must be some people's whole *existence*. I am humbled.

I just got done grabbing basic land cover data for a neoscav style game spanning the u.s., when I came across the MRLC land cover data set.

One file was 17GB in size.

Worked out to 1px = 30 meters in their data set. I just need it at a one mile resolution, so I need it in 54px chunks, which I'll have to average, or find medians on, or do some sort of reduction.

Ecoregions.appspot.com actually has a pretty good data set but that's still manual. I ran it through gale and theres actually imperceptible thin line borders that share a separate *shade* of their region colors with the region itself, so I ran it through a mosaic effect, to remove the vast bulk of extraneous border colors, but I'll still have to hand remove the oceans if I go with image sources.

It's not that I havent done things involved like that before, naturally I'm insane. It's just involved.

The reason for editing out the oceans is because the oceans contain a metric boatload of shades of blue.
If I'm converting pixels to tiles, I have to break it down to one color per tile.
With the oceans, the boundary between the ocean and shore (not to mention depth information on the continental shelf) ends up sharing colors when I do a palette reduction, so that's a no-go. Of course I could build the palette bu hand, from sampling the map, and then just measure the distance of each sampled rgb color to that of every color in the palette, to see what color it primarily belongs to, but as it stands ecoregions coloring of the regions has some of them *really close* in rgb value as it is.

Now what I also could do is write a script to parse the shape files, construct polygons in sdl or love2d, and save it to a surface with simplified colors, and output that to bmp.

It's perfectly doable, but technically I'm on savings and supposed to be calling companies right now to see if I can get hired instead of being a bum :P

real story. In high school, a librarian (women) recommended me a book. I read it in classroom, it was fine for the first half and then.... the real story began.

It was 50 shades of grey.

It's been about 4 years. I'll soon be completing bachelors. And I've yet to return the book, out of shyness.