wylee

I think the reasons are more practical. It's rare that it rains very hard in Portland. Carrying an umbrella throughout six to eight months of the year just in case is inconvenient, and you'll probably end up losing it anyway. A light rain jacket is easier to deal with and also blocks the wind. I don't think pride has much to do with it.

I don't think anyone does `git bisect` all that often, but... when you need to do it, you hope the history is clean. Otherwise, figuring out what went wrong and where can be a nightmare.

I just went to one of my repos on Bitbucket, and it only took me one click to get to the source for master and then another click to get to the source for another branch.

You can also set up a project so the source is shown by default on the "landing page" instead of the overview.

Edit: slight re-wording

The main reason I prefer a lighter bike is for when I need to carry it up some stairs or something like that. For most everyday riding I don't think weight matters much.

I would think that when someone writes a document like this that the context is really important for the record and that they're not so concerned with making an "impact".

Edit: Grammar

I initially only glanced at the about page without reading it, but after I saw your comment, I went back and read the whole thing. Most of it is just (interesting IMO) info about the site and the technology behind it.

Or, at a higher level, maybe their approach to soliciting candidates is wrong. A lot of the job descriptions I see are sloppy. Or they're so vague that you can't figure out what you'd actually be doing (or what the day-to-day would be like). Some of them throw in peripheral technologies just to cover all the bases or something.

It seems like a lot of hiring managers/companies treat a job description as an afterthought when it actually has a huge effect on who applies for a position (_obviously_). People who have more options will tend to ignore the sloppy, vague postings.

The person who wrote this article seems more conscientious than this, but it's something to consider.

I use DRF with Angular at work, so I'm interested in seeing where this series goes.

Tangentially, I can't imagine using Django without DRF. It makes setting up RESTful(ish) APIs so easy. Even if you don't care much about the RESTful aspects, it provides a much nicer way to organize your code than default Django IMO. I especially like how serialization works versus Django forms.

Good point. I'm not sure off the top of my head if Shapely has a specific function for what you're trying to do. It does have highly-optimized distance functions though. Might be interesting to compare those to your version.

One way I've approached this problem that seems pretty fast is to load a set of points into a PostGIS-enabled database, then use the `ST_Distance` function and order by distance.

[Edit]

Shapely solution:

    points = MultiPoint(((0, 0), (1, 1), (4, 4)))
    point = Point((3, 3))
    sorted(((p, p.distance(point)) for p in points), key=lambda item: item[1])

What's really bizarre is that they actually deliver the article content in the initial HTML response. It's just hidden using CSS. You can read it by turning off CSS for the page.

I personally think it's best practice, although returning a generic 400 isn't _that_ bad. Libraries like Django REST Framework handle this automatically.

I have family in the southeastern US who use "anymore" like the person you're responding to did (and they have for decades). I don't think it simply means "now". There's a slightly different connotation that seems somewhat negative. Kind of like: "It used to be like this, but now it's like this... and I'm not sure I approve".