Having only an infrequently-used personal account, I was told by the landing page that analytics would only apply to tweets going forward. Rather disappointing, but I suspect that I'll check in on it from time to time anyway.
Right, given that as yet no DNA from Kennewick Man is available, I believe it's implied that he may have been the product of intermingling between the theoretical first settlers and the later Bering settlers. No revision of land bridge migration dates would be needed.
Well-said; thank you for the reply. Based on what you've said and what the article says and implies, I am inclined to be biased against the tribes in this matter. While there is obviously a long and tragic history that is still in play, it seems to me that if there is an agreement that is in place that allows the federal government (NOT necessarily within the Corps) primacy in determining whether remains belong to some tribe(s), then such tribes have no immediate grounds to claim the remains. I agree that the Corps comes off looking very much like they intended to use the remains as a bargaining chip.
Summary: About 15,000 years ago, sea-faring people made their way from what is now Japan along the North Pacific rim to what is now the First Nations region. It was only later that the Bering land bridge migration occurred, those peoples integrating with the first settlers. This article offers a fascinating look into the intersection of cutting-edge archeology and tribal/governmental politics.
If anybody has any insight into the Corps of Engineer's behavior that was discussed in the article, I'd love to hear it.
The sessions, the wget-like download mode, the binary detection, the upload capabilities... there is a lot to like here. I will definitely be checking this out. Thanks for posting!
"Treading in Python, Vol. 2" by Harrison goes pretty in-depth with the usual suspects -- iterators, generators, decorators, dunder methods, etc. Then Knupp's "Idiomatic Python" is handy to review for tips and tricks. But overall I also like Beazley et. al. for a great cookbook and a good glimpse into "effective" Python.
Good points all. This is what I get for mouthing off from my phone instead of taking the time to think about what I'm saying. I will say though that given the continuing productivity of language, the fact that those earlier examples exist doesn't necessarily preclude my supposition that "X-eer" could see an uptick in neologistic usage - although again you're quite right that it wouldn't be "inchoate" in the sense of not being extant.
I haven't heard this term before, but maybe that's just me:
"... it became clear that ad retargeting—in which you show ads to people who recently visited your website—was where MARKETEERING dollars were going" (emphasis mine).
That's an interesting turn of phrase: it evokes Disney's Imagineers, who can be loosely said to be engineers with a heavily creative bent, and applies it to the act of marketing, thereby implying a more heavily creative and technically adept form of "marketer". I wonder if "X-eer" is an inchoate language trend?
I'm a recent graduate in Computational Linguistics who's looking for an opportunity to do interesting work in various aspects of NLP, as well as general data science and web dev-related work. I also have a background in GIS from a former career and it would be particularly awesome to find a position that allows me to tie mapping and data analysis together. Most of all, though, I just want to get my hands dirty in the nuts and bolts of your app and help you build something cool -- an API, a recommender, analytics tools, or whatever you have in mind. I love learning about new verticals and if you're in a niche industry that isn't "sexy", all the better! At this point in my career, company size isn't a huge issue for me; I feel that I can learn a lot in any situation. Local to San Diego or remote would be great, and my family and I would consider relocating to the Bay Area, Austin, or D.C.
True, true. But the point still stands that there are options which hint at the durability of cockroaches without invoking disgust!
Actually this all does remind me of research on the tangible effect of disgust on products -- see [0]. That work studied physical contact, but it's easy to extrapolate from there.
It's really awesome to see the enhanced Vagrant support, as well as the Angular support. What I am really looking forward to/hoping for, though, is IPython notebook file integration.
Yes, I remember that well. Seeing the animated graphics linked within that article really was an 'ah ha!' moment for me; I'd definitely recommend it as an introductory intuitive motivation.
I feel like I have read most of these in a piecemeal fashion, but seeing all these articles together like this really drives home the importance of paying attention to the basics. Great collection; thanks for sharing!
As someone who is currently looking for a job, I'm slightly annoyed (with myself) that I missed it. There are several salient points already made about its merits and drawbacks, but please consider this a vote for some kind of periodic recurrence. Being that I'm looking for a relatively junior position, I did appreciate @glimcat's comment re: taking job posts at face value, and I think that the possibility of having companies approach a candidate that has previously had no idea where s/he is shooting in the dark is refreshing, affirming, and motivating.
I am currently going through Miguel Grinberg's Flask dev book (the early O'Reilly version) but I had considered diving into Django instead. My rationale for making this choice basically came down to seeing that Flask doesn't "come with batteries", and I thought it would be more educationally valuable to have a broad understanding of the various components of a web app before trying something like Django which apparently does things that Flask doesn't. (I may be off-base here, of course -- I know that I don't know what I don't know!) All of which is to say that I hope you give some space to at least discussing "why Django?". Good luck!
I do this as well, because the cart has the property of notifying me of price changes of items saved in the cart. I'm actually not sure if wish lists do this as well, but as I am in the cart so often (shopping online as much as I do), it's easy for me to keep an eye on items that I might be hesitant about pulling the trigger on.
That's very interesting and cool, but the myth[0] is that a large amount of copies were buried, and one copy found is necessary but insufficient evidence of the myth's veracity.
As a broad first pass, have you looked into LSI and other related topic-modeling algorithms? I am a Pythonista and I like a library called gensim very much for playing in that space; maybe look at the documentation for that and see if it sparks any ideas?
In response to blahah: suppose that you could somehow make the enablers previous recipients of expertise? If you could assess an incoming project's needs and bin it with previous projects, people associated with those previous projects could pay back to the overall effort by trying to help the incoming project decide what the pain points are and how they might be solved.
I agree with emhart -- this was my exact reaction. Of course I understand that you can't launch beta with all your features, but please consider this another vote for a more robust matching mechanism. Other than that, great work! I think this sort of opportunity to get our hands dirty is exactly what a lot of people are looking for.
Everyone's pedagogical requirements vary, and decorators are notoriously hard to explain[0], but seeing something like "A decorator in Python is a function that accepts another function as an argument." as a flat statement at the beginning of the article is an immediate turn-off for me, since I can easily see someone who is still learning about Python in general extrapolating from this to conclude, say, that map(), reduce(), and filter() are decorators as well. It's just a bad start to the article IMO and I didn't bother reading much further.
Certainly true, but there can be a gap between providing such tips and having them be accepted/upvoted. There is probably something to be said for exploring optimizing strategies, along the lines of frequenting the site at certain times, ignoring requests from brand-new accounts that aren't likely to follow through on accepting answers, and so on. Having said that, I am not sure that there is enough to be said about those strategies to be worth the time of maintaining a repo, although I always admire people who are pushing the bounds of what Git can be used for.
This title needs re-editing unless I am missing something. The linked article only details a collapsed building, not a bridge. As it stands, reading the title of the submission alone gives the impression that there is a full-fledged terrorist attack underway, which has not yet been shown to be the case.
My apologies -- I posted this from mobile and didn't see the ad. I should have checked. If you're motivated, I found that deleting the div ids "jpintoverlay" and "jp_lightbox" worked for me.