erex78

This is cool and a nice idea / UI, but it seems to bubble up populations centers. Needs to normalize for population somehow. (https://xkcd.com/1138/)

Try with a better tile: http://nyc.terrapattern.com/?lat=40.7198568&lng=-73.98089090....

It works beautifully.

You might consider adding Mapsense[https://github.com/mapsense/mapsense.js], a library for using tiled vector sources with D3. (I work at mapsense).

We're a small group of ex-phds in computer science and math.

We're working on solving hard mapping problems around vectors and massive datasets. We're backed by tier one VCs. We welcome engineers with background in search, large scale data processing, computational geometry and graphics. Or just smart people who get stuff done.

Right now we're particularly looking for both front-end engineers who can organize complicated SPAs and backend engineers with experience scaling APIs.

Email erez@mapsense.co.

Mapsense Position: Backend Engineer

Keywords: INTERN, VISA, FULLTIME. Minimum education: Bachelor's degree in CS/EECS. Minimum experience: 2 years. Useful to know: Java, Maven, ZooKeeper, MongoDB, Lucene, Git.

Tone A (professional):

The backend team at Mapsense is a small but highly motivated group building scalable tools for geodata analysis. We're looking for an independent, experienced backend engineer to join our team and and contribute while learning the infrastructure. An ideal candidate would be comfortable with designing and implementing web APIs; building and testing autoscaled services; and being productive, professional, and personable on a daily basis.

Tone B (nerdy):

There's a word to describe the freezing of a machine that executes billions of electronic instructions per second, then examining its memory's contents bit, by, bit: debugging. If hitting breakpoints sends chills down your spine, you're probably cut out for backend engineering at Mapsense. Hack away at the backend of a complex but intuitive geodata analysis API, implemented as a distributed, autoscaled nexus of modern open source technologies. And in case joining a team of intelligent, highly motivated code ninjas isn't enough, we have one more guarantee: consider boredom a thing of the past.

Tone C (cute):

The one thing that sets Mapsense apart from all the other geodata startups is the sheer popularity of our cute office dog, Amos. To be honest, our backend engineering team is a little jealous of all that attention. They've already developed a versatile but highly intuitive API for geodata ingestion and analysis, all while placing massive emphasis on documentation, testing, and teamwork. But to really shine, they need some help! Will you be the next independent, experienced engineer to join the backend ranks and help surpass Amos' renown once and for all?

Tone D (challenging):

Tired of companies living off of boring CRUD APIs with a single, static database? So are we. The backend engineering team at Mapsense is building a distributed, scalable backend architecture to support the ingestion and analysis of massive amounts of geodata, but writing well-designed, documented, and fully tested code isn't easy. That's why we're only hiring highly motivated, independent engineers to join a tiny backend team always willing to commit to quality. It won't be easy, but nothing worth doing ever is.

Tone E (meaningful):

Help Mapsense revolutionize the process of geodata analysis by joining our backend engineering team in developing an incredibly versatile tool with use cases in a variety of industries, from climate to marketing to military. You'll have the opportunity to jump into a robust, scalable system built on the latest open source backend technologies, and work with a motivated group of engineers. Expect to grow from interesting engineering problems every day while transforming the world one data set at a time.

How would somebody do this w/ D3? Are there any similar bl.ocks that anybody knows about?

My first thought...

We're a small group of ex-phds in computer science and math. We're working on solving hard mapping problems around vectors and massive datasets. We're backed by tier one VCs.

We welcome engineers with background in search, large scale data processing, computational geometry and graphics. Or just smart people who get stuff done.

Email erez@mapsense.co.

If you want to be/work with engineers and build something real/hard, I would start looking for your next job. Even without professional experience, don't settle, find a place where the standards are up to yours.

(We're looking for engineers at my company if you're interested..)

An Almost-Linear-Time Algorithm for Approximate Max Flow in Undirected Graphs, and its Multicommodity Generalizations:

http://arxiv.org/pdf/1304.2338v2.pdf

Does this bother you? Aggressively targeting your competitor's employees? Imagine if Google went to your startup and offered everyone 100K signing bonus to leave. Would this be OK, within the bounds of acceptable competition?

Winston? http://public.wsu.edu/~brians/errors/churchill.html

HN people might not care about this sort of thing (ending a sentence with a preposition), but it screams out at me:

"We'll make sure everyone knows for whom to buy a present!" vs. "We'll make sure everyone knows whom to buy a present for!"

Good job on the who vs. whom though..