250 karma · joined October 27, 2009
Amazon S3 lists objects in alphabetical order.
Shameless plug, but I made a fun side project that allows Amazon Athena to read SQLite databases from S3. https://github.com/dacort/athena-sqlite
https://github.com/dacort/athena-sqlite/blob/master/lambda-f...
Implemented the VFS side in Python, thanks to the awesome apsw library.
I've giving this one a shot, might have too much functionality for me though...I liked how bare-bones the other one was. https://chrome.google.com/webstore/detail/json-viewer/gbmdgp...
They had a demo of Github realtime activity and I hooked it into a bunch of different events around the org - Salesforce/Yammer/Github/JIRA - was neat to have a "pulse" of daily activity in the background.
Per https://en.wikipedia.org/wiki/Washington_State_Ferries
> The agency maintains the largest fleet of ferries in the United States at 22 vessels, carrying 23 million passengers in 2014. As of 2014 , it was the largest ferry operator in the United States, and the fourth-largest ferry system in the world.
I'm co-founder of a local startup here w/~140 people and that's pretty comparable/above average to what I've seen depending on the cash/equity split. The big co's (Facebook, Amazon, Google, Twitter, et. al) will be higher than average due to the nature of how hard it is to hire good folks here.
Seattle is fantastic for people that enjoy the outdoors - hiking, backpacking, rock climbing, ski/snowboarding, camping. The closest ski/snow area is 45 minutes from the city. It doesn't get _too_ cold in Seattle proper - usually around 40° F. The nice thing is that you have the mountains nearby, so if you do want the cold weather it's a quick trip.
One word of caution around UW - your age is definitely on the higher end of other people that will be living in that area. Although the rents are cheap, that's usually for a reason. Reddit is a great resource for info on moving to Seattle --> https://www.reddit.com/r/Seattle/wiki/index
Got it up and running easily enough, and connected to Redshift. But seemed like creating a new "slice" required custom JSON params to define it. Unless I missed something?
edit: yep, missed something. Can "explore" a table by clicking it's link in the table listing.
My experience (Series C, ~130 employees) echoes many of the points in this article.
<meta property="twitter:item:variant1:id" value="n6NDAWFNqjkNZftJWq0BQw==" /> <meta property="twitter:item:variant1:title" value="Small" /> <meta property="twitter:item:variant1:inventory_count" value=1 /> <meta property="twitter:item:variant1:price" value=75000000 /> <meta property="twitter:item:variant1:tax_category" value="included_in_price" /> <meta property="twitter:item:variant1:last_updated" value=1409259500000 /> <meta property="twitter:item:variant1:attribute1:text" value="Small" />
I have yet to test it in production, but it looks pretty promising.
I had a lot of problems with EM blocking networks connections if an event loop was tying up CPU, but I suppose that's to be expected.
http://railstips.org/blog/archives/2009/02/02/bedazzle-your-...
Ya know, just in case you want to upvote it.
Most people don't. They'll type "facebook" into search instead of going to facebook.com.
If the search is good enough, the url isn't necessary.