geweke

5 ms·

1.
by geweke 12y ago
YES. Everybody deserves this. As a manager, I try extremely hard to make sure this happens. The way I think of it is this. On the day you are fired, when you get called in a room, if I ask you, "why do you think you're here?"
2.
by geweke 12y ago
Thanks so much for replying. My concern wasn't about permission -- I'm far from protective of my talk; hey, more distribution is great! -- so much as it was the appearance of the site. (And even the video -- you overlaid your logo
3.
by geweke 12y ago
What rebelidealist said. In the talk, I try to be pretty clear about what kinds of data are a good case for this kind of storage and what aren't. (In short? Data you only ever retrieve for a single row at a time, and that you never que
4.
by geweke 12y ago
Thanks for posting this. For what it's worth, I'm the author of this talk and the one pictured in the video. I'm flattered it's getting so much attention (I like having my ideas spread!), although there's one thing
5.
by geweke 13y ago
It's not Django, but I've built something quite similar for Rails, and have really loved using it. The combination of RDBMS stability and the flexibility of schemaless content is really powerful -- it is (IMHO) the best of both wo
6.
by geweke 13y ago
I'm more than happy to answer any questions about this gem. It was built as the result of ~2+ years using Mixpanel intensely with Rails, seeing the scaling challenges that result, and then tackling them. I'd love to help anybody e
7.
MetaEvents for Rails: DRY Up, Structure, and Document Your Mixpanel Events(swiftype.com)
16 points by geweke 13y ago|2 comments
8.
by geweke 13y ago
What, in particular, is problematic about them? Do you mean their particular implementation, the fact that they aren't also encrypted, or the general "password equivalent in a cookie" concept overall?
9.
by geweke 13y ago
Nice! Thanks for turning me on to that -- I've been looking for something like that. I actually think they're pretty different problems. WebServerUid is about uniquely identifying a single browser over hours, days, months, or year
10.
by geweke 13y ago
Sure thing -- I built it because I needed it, but I'm really happy to be able to share it, too. You definitely could use this for trial/demo accounts, too. You'd want to think carefully about abuse prevention, I suspect, but
11.
by geweke 13y ago
Really good point. Even better, I'd really like these cookies to be digitally signed (like Rails' session cookies are by default), so that they're unforgeable. Seems like it wouldn't be too terribly hard to add to nginx.
12.
by geweke 13y ago
I'm the author of this gem -- more than happy to help out with it. The problem it solves is small but important, and this is now the third company at which I've solved it...so I'm sure there are more folks out there dealing w
13.
WebServerUid: Easy Unique Browser IDs for Rails(swiftype.com)
20 points by geweke 13y ago|11 comments
14.
by geweke 13y ago
Nice, Steve! Always good to see validation of the idea in both directions. :)
15.
ObjectIdColumns: Transparently Store MongoDB BSON IDs in a RDBMS(swiftype.com)
6 points by geweke 13y ago|3 comments