3 ms·
Pet peeve: the verb is designing. Besides that, let me rephrase here. At <west coast startup, essentially a copy of earlier successful European businesses suc
by contingencies 12y ago
Pet peeve: the verb is designing.
Besides that, let me rephrase here.
At <west coast startup, essentially a copy of earlier successful European businesses such as HouseTrip, but with access to stupid amounts of US capital and therefore more profitable>, we <make superfluous, keyword-laden, unverifiable claim about ourselves in the future>. We <continue to integrate feel-good community pronouns>. We <here discuss something only tangential to our core business and assert that we have allocated at least two people to this area>. We <have nothing better to do than write it up, because quite frankly, there's nothing more pressing for us to work on in an already automated business of relative simplicity>.
OK, so that's a bit harsh, but there's some points toward reality in there. Sorry, as someone who used to run a complex travel industry business (3200+ hotel contracts... all of them in Chinese, all business by digital fax (no convenience here!), constant rate changes, in 6 human languages and multiple currencies with a real time call center) and who co-pitched for VC with HouseTrip's management in London in 2009, I just have very little respect for AirBNB.
- baddox 12y agoUnder what definition? The word "architecting" to me connotes both the design and the implementation of a system.
- contingencies 12y agohttp://blog.oup.com/2008/07/architect/ http://blog.oup.com/2008/07/architect/
- voronoff 12y agoCare to do a write up of what you're doing as far as fraud prevention goes? However you feel about Airbnb, this was an interesting post. It's not ground breaking or earth shattering, but it shows the tech stack that a large company is using to solve a real problem, and that's useful. They even did a fairly good job of explaining the why.
- contingencies 12y agoCare to do a write up of what you're doing as far as fraud prevention goes? Sure, but only high level. I would hazard a guess that fraud prevention is a lot more complex for us at https://www.kraken.com/ https://www.kraken.com/ ... dealing with many cryptographic currencies and conventional currencies spread across probably over a hundred legal jurisdictions is not easy. We likely have to consider far more factors than these guys. We have recently added two more quants from programs highly regarded in the conventional finance industry to our team, plus we have over seven figures of investment in legal and training programs in the area. We also use R. Basically, it's inputs (behavior), processing (metric extraction, risk model), output (boolean choices, statistical cluster membership, etc.)... where a series of such outputs may feed in to a heirarchy of scores for different elements within a system. Some applications may be real time, others after-the-fact. At a high level, which is mostly where my involvement is in hiring people, fraud prevention is not dissimilar to spam or intrusion detection: you can basically use a combined, constantly tweaked set of inputs to a Bayesian-style scoring algorithm. Inputs include both static rules and statistical anomaly detection. http://en.wikipedia.org/wiki/Bayesian_probability http://en.wikipedia.org/wiki/Bayesian_probability