Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
avibryant
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
by
avibryant
14y ago
Etsy - Remote - Hadoop I'm looking to expand the team that makes Etsy's big data infrastructure awesome, reliable, and easy to use, supporting search, personalization, analytics, and many other product teams throughout Etsy. We work primari
32.
▲
by
avibryant
14y ago
Yep, though a feature request I've put in is to respond to a ctl-c by producing the results from the stream so far... that way if it's taking a while on a large file you can interrupt and still get something useful.
33.
▲
by
avibryant
14y ago
Etsy - Remote - Seller Economics We're building tools to understand Etsy's marketplace and help Etsy's 800,000+ active sellers operate better, more efficient businesses. We need hackers who can learn enough economics to ask the right questi
34.
▲
by
avibryant
14y ago
Kiva probably would have been worth a mention in my post, yes. Etsy is where I could see an obvious way for me to have an impact, and so could they.
35.
▲
by
avibryant
14y ago
That's much broader than the truth: what I can claim credit for is Twitter's adoption of Scala for Hadoop jobs (and the Scalding framework that resulted from that). Scala services were already in heavy use at Twitter long before I got there
36.
▲
by
avibryant
14y ago
It has not been. I'm not starting myself until mid-June, and I do expect to be doing a bunch of hiring.
37.
▲
by
avibryant
15y ago
Ok, so Cascading has a slow implementation of secondary sort, but is there any reason you believe that couldn't be improved? I don't think you're really comparing architectures there, just how well optimized particular implementations are.
38.
▲
by
avibryant
15y ago
Can you give an example of a job that would be difficult or impossible to perform efficiently with Cascading, but Pangool gives an advantage over raw MapReduce?
39.
▲
by
avibryant
15y ago
Everyone voices this concern, but it's important for people to understand that most Smalltalkers consider the binary image a throwaway artifact, and sometimes a deployment mechanism - it is emphatically not how you store or distribute code.
40.
▲
by
avibryant
16y ago
See http://trendly.com . Sadly, I don't believe the site is operational any more.
41.
▲
by
avibryant
16y ago
Neat. The doIt method is still quite central to Smalltalk systems.
42.
▲
by
avibryant
16y ago
Wait, where's the link?
43.
▲
by
avibryant
16y ago
With Smalltalk? Sure. With Seaside? No, that's not what it was designed for. I haven't yet convinced Twitter to do a rewrite in Smalltalk ;). But it would be a step up from Ruby, even if only to get a better garbage collector.
44.
▲
by
avibryant
16y ago
We solve it by building Smslltalk-specific version control. Monticello, which cwp and I built for Squeak, is a Smalltalk-only DVCS that predates git and hg and has become the de-facto standard. Earlier systems include ENVY and StORE. After
45.
▲
by
avibryant
16y ago
Not enough info here to give much concrete advice, but if it's helpful to talk to a fellow Canadian who's been through all of this, feel free to ping me privately with more details (avi@twitter.com).
46.
▲
by
avibryant
16y ago
Absolutely true for some apps (and for those apps, in Seaside as in any other framework you can do the extra work to get bookmarkable URLs). For other apps, it's nice not to have to worry about this. For example, when did you last email som
47.
▲
by
avibryant
16y ago
Here's the experience of debugging in Seaside: 1. You reload a buggy app in the browser. 2. Oh noes, you hit an error: the browser shows you the stack trace. 3. At the top of the stack trace, there's a "debug" link: if you click that, the H
48.
▲
by
avibryant
16y ago
As a Canadian (though currently living in the US), that last sentence is both astonishing and scary.
49.
▲
by
avibryant
16y ago
This info has always been available: the RSS feed attached to everyone's profile page is by ID. For example, mine is feed://twitter.com/statuses/user_timeline/13192.rss
50.
▲
by
avibryant
16y ago
I've been puzzled by len() and company for a long time and this is the most complete and sensible explanation I've heard. Thank you. I still think it's the wrong design, mind you, but I no longer think it's a crazy one.
51.
▲
by
avibryant
16y ago
The great thing about the box being so tiny is that expectations are correspondingly low. To write an essay or even a blog post, you need to think through an issue in a fair amount of depth. Among other things, Twitter is for those half-for
52.
▲
by
avibryant
16y ago
If only I could get @avi for myself as easily as I got @paulg for Paul.
53.
▲
by
avibryant
16y ago
This sounds like a fixable problem. What would some acceptable variants of your name be? If you email me (avi@twitter.com) I will see what we can do. I'd certainly love to see you on Twitter.
54.
▲
by
avibryant
16y ago
Why not consider it a reader macro, and translate it to (@ foo bar) or whatever is appropriate, before applying macro expansion?
55.
▲
by
avibryant
16y ago
Some reasons I can think of: it's definitely an advantage to be able to compile the code on the client-side, which sibilant should be able to do; I don't know if Parenscript can bootstrap itself the same way. Some people, like me, prefer li
56.
▲
by
avibryant
16y ago
The "French language" may follow, but the Quebecois sure don't... (so, yes, French has exactly the same issue).
57.
▲
by
avibryant
16y ago
What's the URL? I can try to look into the discrepancy.
58.
▲
by
avibryant
16y ago
Yep, although in some cases if he had, I would have been annoyed at being quoted making an unqualified statement when I was intentionally making a qualified one.
59.
▲
by
avibryant
16y ago
It's odd to see my verbal tics rendered faithfully to text - the number of times I say "sort of" and "kind of" in this is quite scary.
60.
▲
by
avibryant
16y ago
raganwald, you answered "can we do away with blocks". What about "can we do away with lambdas"? Going by return semantics, Smalltalk has only blocks, not lambdas. I find that constraint bites me far less frequently than Javascript's opposit
More ›