634 karma · joined February 16, 2010
Ruby, R, Python, Redshift, Postgres, Scala
Avant Credit Corp ('Avant') is a fast-growing startup that offers tremendous advancement opportunities to its employees. Since its launch in December 2012, Avant, a consumer finance company, has changed the way customers borrow money -- providing them with a new and unique online experience. Avant uses state-of-the-art analytics methods in order to offer its lowest possible interest rates to the widest range of customers. Since inception, Avant has secured over $300 million in equity financing and over $700 million in debt financing to continue to grow at an exponential pace. Previously, Avant's founders created the leading international online short-term lender currently employing over 1,000 individuals and generating over $700 million in annual revenue. Avant’s founders have also launched an innovative real estate investment trust that provides affordable housing options in Chicago, Indianapolis and Baltimore with over 10,000 apartments owned and managed.
Please apply at https://www.avant.com/jobs
Clojure, ClojureScript, R
ReadyForZero's award winning product and blog helps consumers get out of debt. We've helped hundreds of thousands of people pay off >$200M in debt. We were recently acquired by Avant, a Chicago-based online lender to offer our product to their borrowers and are hiring aggressively in Los Angeles.
Please reach out at jobs@readyforzero.com
EDIT: s/composed functions/composed logic functions/
Maybe google "machine translation segmentation" or OCR for references to papers on the topic, but methods for doing this are really successful (especially on english).
What more could you do if you didn't need to deploy your entire stack with each little change you make? If you could only deploy your frontend (in different versions simultaneously) pointing to a backend that's always up, it enables much faster iteration: testing, bugfixing, demoing things that otherwise you might not deploy different versions for because it's too painful.
For example, you could A/B test meaningful portions of frontend code in a more scalable way than, say, Optimizely. Or you might point a user that's having problems to a specific build (which you can deploy instantly) and see if it fixes their problem _on their live account_. Or you can hack together a new feature that works _on a live account_ for a presentation, and push it without worrying about mucking up or interrupting production traffic. Or turn off minification instantly and deploy that.
Plus, you don't have to worry about refining internal frontend build scripts, it's plug and play.
If you have any specific questions, email contact@readyforzero.com.
Disclaimer: I work with the author, and it's suprised me how much of a 'science' it really is (hypotheses can be tested, and the results can be measured and improved)
Yet another reason I worry that Python 3 may fracture the community...
Counter-intuitively, I've also noticed in many cases that using binary search over sorted elements in contiguous memory is actually faster than using a hash table at all.
Has anyone else found this?
One natural reason that this situation has gotten worse is that the credit card market has become completely saturated (everyone who wants a card has one [almost]). This, combined with relatively easy credit recently has resulted in the card companies marketing to people that they would previously had stayed away from.
We've learned that people often become accustomed to credit at an early point in their lives (college), rely on it for awhile, then don't suffer any explicit repercussions, and so grow accustomed to it until the problem grows and it's too late.
I don't really think it's a 'conspiracy' either, since it's clear what the motivations for all of the involved parties are.
Would love to chat about this more, but I need to tend to the serverz :)
(1) http://www.bos.frb.org/economic/ppdp/2009/ppdp0910.htm (2) www.federalreserve.gov/pubs/bulletin/2009/pdf/scf09.pdf