ericwaller | 3 years ago | on: Attempting to create an aesthetic global line breaking algorithm
ericwaller's comments
ericwaller | 3 years ago | on: Record labels dig their own grave, and the shovel is called TikTok
The slightly longer answer is that we'll probably be the strongest option for smaller venues that want to do more complex stuff. To the extent that there's always some tradeoff between simplicity and power, we're likely to continue to lean pretty heavily on the power side for our core ticketing system.
ericwaller | 3 years ago | on: Record labels dig their own grave, and the shovel is called TikTok
It's amazing how many ticketing systems of various forms have been built over the years. It seems like one of those things that should be simple, but there are just so many ways to slice it.
ericwaller | 3 years ago | on: Record labels dig their own grave, and the shovel is called TikTok
ericwaller | 3 years ago | on: Record labels dig their own grave, and the shovel is called TikTok
While we're probably better known as a consumer app for buying tickets, SeatGeek also builds the full set of software you need to run a major venue. Everything from issuing and managing season tickets for the resident pro sports team, to working with promoters in selling tickets to their national tours and hosting the big, high-demand concert on-sales that accompany them.
A big component of our path into the market is that it's often the resident pro sports team that operates the venue and makes the ticketing decision. They tend to be very focused on the fan experience, particularly for season ticket holders, and that's our strong suit.
ericwaller | 3 years ago | on: Record labels dig their own grave, and the shovel is called TikTok
ericwaller | 4 years ago | on: So you want to build a carbon capture company
ericwaller | 5 years ago | on: Edge Computing
But latency (mostly) aside, there seem to be a lot interesting use cases for what is more or less programmable CDN configuration. Particularly when you have a relatively straightforward application (architecturally at least), but want to tap into the very distributed, very scalable CDN layer for little bits of critical functionality.
ericwaller | 5 years ago | on: Why can't I sign in with Facebook anymore?
It was indeed Apple's "Sign In with Apple" deadline that prompted us to make the change (for those who don't know, apps that offer sign in via a third party auth mechanism will also need to offer sign in with Apple), but it's something we've considered on and off for many years.
Two big reasons. The first is that when we work with pro sports teams, fans of that team are able to sign in to their team accounts using SeatGeek. Having Facebook, and potentially Apple, also in the mix there felt like it would lead to a lot of confusion. The second is that while we've seen that sign in with Facebook leads to more sign ups in the first place, we've also seen that it causes confusion for users who are later unsure how they initially signed in, and that confusion can hit just as they're trying to pull up their tickets outside of an event.
ericwaller | 6 years ago | on: An earthquake will destroy a sizable portion of the coastal Northwest (2015)
ericwaller | 10 years ago | on: Ask HN: Planning to leave. How best to handle stock options?
But yeah, definitely talk to a CPA.
ericwaller | 11 years ago | on: Show HN: Fast autocomplete service written in Go and JavaScript
We're using elasticsearch now which is definitely a bit more of an operational headache.
ericwaller | 11 years ago | on: Official Go support
ericwaller | 12 years ago | on: SideCar's Kalman Filter models San Francisco brunch
1. http://chairnerd.seatgeek.com/using-a-kalman-filter-to-predi...
ericwaller | 12 years ago | on: Cross-Event Search
ericwaller | 13 years ago | on: APIs are Dead, Long Live APIs
[1] http://www.travolution.co.uk/articles/2012/04/04/5576/open-a...
ericwaller | 14 years ago | on: Interview Heuristics
I think something that a lot of the recruiting/hiring discussions on HN miss is that the hiring process is not only about finding people who are capable of doing the job. It's also about finding people who will thoroughly enjoy doing the job and get along well with the rest of the team.
For example, I spoke to a candidate (in other words he made it through this set of heuristics) whose background was in security and whose primary platform was windows. He was definitely very bright and very well accomplished, but by the end of the interview, I genuinely thought he would have been bored out of his mind at SeatGeek.
Similarly, if you don't use at least one of OSX, git, ruby or python, there's a decent chance SeatGeek just isn't for you. An important caveat, that should probably be in the post, is that if your answer to any of the specific-tech related questions is "no, but I saw that you use X at SeatGeek, and I'm interested in learning more about it", that's probably equivalent to a "yes".
ericwaller | 14 years ago | on: Right versus pragmatic
ericwaller | 14 years ago | on: Deprecating Use of the "X-" Prefix in Application Protocols (IETF Draft)
employ meaningful but currently unused names
ericwaller | 14 years ago | on: How I got into MIT when I was 14