dacort

Gave the S3 functionality a try - it returned objects in reverse alphabetical order. :(

Amazon S3 lists objects in alphabetical order.

Metabase 47 also has new serialization features in paid editions that allow for git-based workflows. https://www.metabase.com/learn/administration/git-based-work...

A while ago I wrote an Athena connector for querying SQLite in S3. ;) https://github.com/dacort/athena-sqlite Uses a similar approach.

SQLite is amazingly prevalent as well. Your own phone probably has hundreds of SQLite databases on it. One challenge with SQLite, though, is you have to download the whole thing to make use of it.

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

As part of a fun side project to make a SQLite driver for Athena, I made a read-only storage driver for S3.

https://github.com/dacort/athena-sqlite/blob/master/lambda-f...

Implemented the VFS side in Python, thanks to the awesome apsw library.

Yea, my guess would be that's it. Coupled with the fact it hasn't been updated in ~3 years.

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...

Reminds me of the (sadly) now defunct choir.io. Intro post > https://corte.si/posts/choir/intro/choir.html

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.

It's one of the largest ferry systems in the world.

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.

At what level, company size, and cash/equity split?

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

Second this recommendation. Very easy to get up and running - may not be able to handle some complex use cases, but for the basics it's fantastic.

Would very much appreciate that as well as walk-through docs.

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.

Great insight into the changing landscape of a CTO as a company grows through rounds of funding in the first several years.

My experience (Series C, ~130 employees) echoes many of the points in this article.

Interesting seeing the activity on Twitter and how quickly Periscope caught up once it was released: https://twitter.com/dacort/status/582570506043310080

Different use case (SMS stats), but you can see an example of querying the local iMessage DB here: https://github.com/mroth/grayratio

I think one of my favorite things about this is that it actually makes product information available in the meta tags.

<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 was a little confused that an "author" rel would be retrieved from a "people" resource. Is there a way to define that author's are people other than the client knowing this?

s/privacy/qa or your discipline of choice that is seen as "slowing down" development. While most devs should be thinking about this, you're correct in that their culture generally doesn't encourage them to.

Something every dev should be thinking about, but rarely is.

Another "missed" option: Got seed funding to pay the bills until it ran out or the company became profitable/raised another round.

Touché

Why not: http://checkip.dyndns.org - About as plain as you can get.

I just replaced an EventMachine-based project with Celluloid::IO - it was a pretty simple replacement, although I had some issues with concurrent connections (https://github.com/celluloid/reel/issues/11).

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.

Not guaranteed to not break: curl -s http://randomfunfacts.com | grep "<td border" | sed 's/<[^>]*>//g' | sed 's/&nbsp;//'

I also find it very helpful to spiff up my prompt when changing into a git repo:

http://railstips.org/blog/archives/2009/02/02/bedazzle-your-...

I'm pretty sure it's been this way for quite some time now...

Client-side encryption feature request: https://www.dropbox.com/votebox/21/client-side-encryption

Ya know, just in case you want to upvote it.

That works for you because you know how the web works.

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.

That didn't answer the question. Just because you don't store credit card information doesn't mean there aren't steps you still have to take to protect cardholder data. PCI compliance applies to both storing and transmitting cc info.

While I understand that real-time full-text indexing is a much more difficult problem to solve, I've got just under 1.5 billion tweets "indexed" in TweetStats. And I'm one person.

Granted, given the 30MM/day number they must be growing that index very quickly and they've likely hit that 1.5 mark pretty darn quickly.

That acquisition didn't actually happen. It was just rumored and TC never updated their article.