175 karma · joined March 14, 2012
https://ali-alkhatib.com
For what it's worth, I tend to tell these people apart from the people with business in the building by noting where they're looking (tourists seem to be looking all over the place like they're taking it all in; people with business at Gates seem to be looking for numbers and other navigational indicators in line with tzs's comment).
0: http://www.nbcbayarea.com/news/local/UberX-Driver-Accused-of...
1: http://laist.com/2015/04/10/uber_driver_attack_van_nuys.php
2: http://www.forbes.com/sites/ellenhuet/2014/06/03/uber-driver...
As an aside, TV Tropes doesn't use HTTPS as far as I know (and according to this too [0]), so none of the show/movie links resolve unless you go in and remove the prefix and let the browser figure it out. Looking at your source, it seems you could just change the "https://" to "http://" or even "//" (although this would break when(/if) you start using HTTPS down the road).
[0]: http://tvtropes.org/pmwiki/posts.php?discussion=13461707110A...
If I need to open something, I'm much more likely to open another tab of my browser and dump queries (especially things like exchange/conversion rates) into Google. It's a shame, too, because the demo here is really persuasively showing that this can automatically do stuff I previously assumed necessarily takes an extra brain cycle or two.
There's also the issue that among languages like Python, standard libraries (like multiprocessing[0]) make parallelizing code trivial (even with/despite the dreaded global interpreter lock). I rewrote some of the code the author uses and on a smaller number (6710886 instead of 67108864) I'm seeing ~1/3 the time to run compared to his baseline with 4 worker processes (27.469517s vs 1:25.373176). I haven't looked into what might be keeping it from being a full 4x faster, but my hunch is that it's a combination of other things going on in my laptop and the undeniable difference in execution speed in cPython (specifically, cPython3.4).
One might make the argument that this is a wildly unfair comparison, but my bigger-picture argument is that a language that abstracts things like parallelization to the point that one can invoke such features in a line or two of added & changed code is probably worth factoring into an analysis, if we're even interested in analyzing languages in this way.
If we're going to write C-like code and run it as Python, should we be surprised when it doesn't live up to those expectations?
[0]: https://docs.python.org/3.4/library/multiprocessing.html
My question was whether there's a policy suitably fine-grained to let me whitelist an app (or a certain type of notification) so that it can get around Do Not Disturb mode and reach me without having to completely shut down notifications from other apps in the settings.
I think there are probably good reasons not to provide context for your posts, just like there are times that it makes more sense to post anonymously (or pseudonymously), but I don't think this post makes a good case for removing context like post date by default.
Can you explain how sync differs if you use Git as your sync arrangement vs Dropbox? I know that Dropbox will propagate changes automatically, but git shouldn't, so would I have to go in and commit/push/pull changes if I opted for git, or does this make a decision about when to make these changes?
1) There's been some research about the demographics of crowdworkers [1] that questions whether it's a representative sample of any particular population, and I wouldn't immediately concede that conclusions drawn from these survey results are externally valid.
2) There's at least a little controversy around how well (or rather, poorly) crowdworkers are paid and treated, with workers on Amazon's Mechanical Turk going as far as crowdsourcing a set of guidelines for academic requesters to right some pretty egregious wrongs that have happened in the past few years (disclosure: I was involved in the research [2] that facilitated those guidelines).
I wouldn't necessarily forsake this data or anything learned from it, but these concerns make me wary to use it myself very readily.
Does anyone else have concerns? Am I just being hyper-vigilant because this is a personal research interest? I'm open to accusations that I'm biased, at least in this case :P
[1]: Ross, Joel, et al. "Who are the crowdworkers?: shifting demographics in mechanical turk." CHI'10 extended abstracts on Human factors in computing systems. ACM, 2010.
[2]: publication/citation forthcoming; for now, a link is easier -> https://ali-alkhatib.com/media/papers/pn2032-paper.pdf
For what little it may be worth to anyone reading this who is(/was) thinking about coming to Stanford, I have heard professors and grad students talk about ways to be more inclusive in their actions and language. I've heard my advisor stumble over "you guys" only to stop and correct himself with "you all". I can't speak for every lab (there are numerous, each with different cultures and norms), but hopefully I speak for everyone when I say that we grad students and the professors are at least open to learning about how we can make the CS program (and the field as a whole) a safer space for everyone, if not actively working toward that goal. If nothing else, we can promote an inclusive culture in how we speak, behave, and in what behavior we (don't) tolerate.
For Lea (and for countless others), I worry her perception of CS has been irreparably damaged. Hopefully that won't be the case going forward.
I've debated where to go from here in my thoughts, and I think the issue I'm struggling with is that the use cases seem different. When I think about "snoozing" something (e.g. Google Inbox, a conventional alarm clock, etc.) I find that the common denominator is that someone or something else is on the other side waiting on me. If nobody was expecting me in lab, I'd come in whenever I woke up naturally (and I do). Similarly, I snooze an email in Inbox (when I do) because someone's on the other end waiting (with some variable amount of urgency) for my reply. A silent "deal with these later" folder would become a black hole, or at least would have a molasses-slow turnaround time.
Given this preconception, I'm not entirely convinced that "snoozing" is the right solution to the problem I'm assuming you're trying to solve (ie trying to help people keep track of and get through all the cool stuff they see on the Internet, right?). Instead, you kind of want to find the gaps in people's time and fill it with the right article for that stretch of time (which is difficult to do for myriad reasons).
I think something along these lines that would be interesting would be an extension that prompted you to catch up on your queue after a few minutes of browsing unproductive sites (e.g. Facebook, HN, Youtube). Even better, if the user could give it a list of sites and say "if I'm browsing any of these sites for more than 5 minutes, please remind me that I have a queue of webpages I wanted to read."
These are just initial thoughts, and I apologize if it's overly critical. I like the idea, and there's a lot of potential here. It's also entirely possible I'm just flat out wrong (and if someone has different experiences or insights that conflict with mine, I'd love to hear it).
The original link was to the animated gif within that post
If you're typing a path (let's say to ~/Dropbox/Public/...) you can say "cd ~/d/p" and hit tab to fill in even the intermediate parts. Given that the only path that matches "~/d./p." is ~/Dropbox/Public/, zsh will fill that in. If it hits an ambiguity down the proverbial road, it'll expand until it hits the ambiguity and list potential matches.
It's really convenient knowing that I can say something like "cd ~/d/c/s/c" and it'll fill in the rest.
edit: I tried to indicate a basic regex pattern but I think HN is reading it as trying to italicize "/p." instead. I later tried escaping it with backslash, but no luck. Sorry if that's really confusing.
There were a few caveats that prevented The Wire Cutter from recommending any monitor, but some of those don't seem to apply as readily now as they did at the time of last edit.
I got the Dell UP2414Q - a 24" ~4k monitor, making it around 183 ppi. The primary issues The Wire Cutter brought up in their rundown (of this display and generally) seemed to be the following:
- price (in this case $1100)
- the resolution being too high for the screen space
- poor refresh rates (30Hz in this case)
On the first point, you can now get it for around $750, maybe less, in the US. The second point was somewhat platform-specific, but on OS X you can tell it to display in HiDPI mode and it'll deal with the resolution in pretty much the same way that it deals with a retina Macbook Pro's 2880x1800 display. Namely, it'll scale everything at 2x. This is idyllic. If you have an rMBP, imagine that kind of sharpness across a 24" display and you're in the right ballpark.
The last point, about refresh rates, is trickier. My understanding is that this display has no trouble displaying at 60Hz once you enable it, but I have this display hooked up to a hackintosh, so myriad driver quirks make it impossible for me to say definitively whether the video card, the monitor, or the whole universe is conspiring against my success in trying to get it to display at 4k@60Hz. I think it's the buggy nature of the solution I came upon, which I could only describe as "not working in varying degrees". I'm still looking around, but I'm not optimistic for a real fix to get 60Hz for another month or two, if I'm lucky.
If I had a 2013 or later rMBP, I understand I could test it since that supports the DisplayPort 1.2 standard, but mine is from 2012. So I'm stuck testing with a desktop that shouldn't really even exist, heh.
So bringing it full circle, I recommend that you give waiting a chance. The Dell monitor I have has been fantastic, but not without its frustrations. If you can wait 6 months (or better yet, a year) I emphatically believe that the long term solutions to these kinds of displays will have shaken out by then. DP 1.2 and HDMI 2.0 will almost certainly be ubiquitous in video cards and probably in most laptops. It'll just be a lot easier to get things up and running.
That being said, if you're willing to put in some work and get frustrated a couple of times along the way, the reward is quite nice.
To the author, you can avoid this by using a "protocol relative URL" (instead of calling for http[s]://... you would call for //...).
More details here: https://stackoverflow.com/questions/4978235/absolute-urls-om...