I got it up and running in dos box - it still runs smooth as butter: https://github.com/phyous/DOS-1.0
HN user
wpnx
gradient descent function
I’m curious what humans at the time would have felt, if anything.
Thank you Simon
Interesting this is top of HN but no comments.
A lot more folks interested in the answer than able to answer perhaps.
West coast is affected as well
I wonder what the advantage is of a blood based test over existing saliva based hereditary cancer screens (that do genome sequencing instead of 23andme type array testing).
e.g: Color genomics https://www.color.com/cancer
I’m curious if there is a user segment truly interested in this feature/product and what their use case is. Naively this feels like a situation of “why on earth would you do this?”
I wouldn’t hold out on paypal coming to US Stripe integration. I believe it’s available in Europe because of legislation requiring Paypal to support this.
I was pleasantly surprised the solution wasn’t “crypto” given this is an a16z article
I bet i’m not the only one that was looking through comments for this.
Anyone else incredibly amused by the tone of this article?
Scaling is hard - I empathize with them and wish godspeed.
I agree with some of the sentiment here, but at the end of the day i’m not sure i’d be able to make a clean cut like OP suggests.
Python is used in so many places that’s it’s part of the lingua franca of programming. I’ve worked at multiple ruby shops over the last few years and pythons still been there in force for data applications.
I much prefer other languages (Ruby, Kotlin), but at the end of the day i need to be comfortable with the language that will be spoken for years to come.
One concrete way of measuring this - how many of us here in comments skipped the article to read a summary
Congrats Jarred :) It's been fun watching you build this over the last year on Twitter. Cheers to much success
Curious; where did you get the 10% number from
Your internal data might not be consistent with what is stored in Stripe. Since Stripe is the one processing the payments, it is ultimately the source of truth for all data regarding whether or not transactions went through, failure reasons, disputes... etc.
The act of reconciling the list of transactions you have stored in your database with what the source of truth has is an important process for finance teams.
Sorry but not seeing how they're different.
From the founder's post:
1- When customers repay their loans, they can be eligible for larger loans at lower rates (it is almost unheard of for payday lenders to offer better terms).
2- In the top half of our Ladder, customers have the option to have their payments reported to the credit bureaus (payday lenders don’t report).
3- When customers need more time to repay, we don’t charge them extra (payday lenders use rollovers to make more money when their customers struggle).
4- When customers make successful repayments, many can become eligible for a credit card (which is essentially an interest-free short-term loan, if paid on time and in full).
Mirror in google cache: http://webcache.googleusercontent.com/search?q=cache:6rWGz01...
It really kicked the llama's ass.
I kind of wish each section was a little longer. This would make for a great book :)
BB is beyond fiscal discipline IMO.
It's pretty clear they'll be gutted and sold for parts at this point. They're trying to lose weight before the fashion show.
Well written, well documented code. Kudos.
It makes sense that this sort of thing is easier if you own a larger project. That sounds like a great way to EDBC = Every day be coding.
A really interesting experiment, and congrats for sticking to it for so long!
The tone of the article is a pretty negative. Perhaps you could end with some suggestions of your own for Microsoft's way forward.
Link is broken, I think you meant this: http://rt.com/news/brazil-argentina-cyber-defense-879/
Looks like the driver got scared and tried to run away. I think the media is making a bigger deal of this than they should.
Don't ask them to write binary search code if they're being interviewed for a front-end position, ask them to build something. +1!
Thanks for the thoughtful response; I really love the way you worded this.
I agree with what you're saying; the best, most fun, challenging and fair interviews I've had have been at small companies coding side by side with somone. I wonder if it's possible to scale the "build-it" interview up to a google sized org.
Another idea I've been mulling around is hiring people for an N month contract position where you get to work with them. If at the end, both parties agree its a good fit, then proceed. I can see a lot of pit falls to this approach, but it might work really well for people with strong referrals.
Great article :)
Maybe not secrets, but lessons learned from the current state of the industry. Each one of the points I make is either from a mistake made in an interview I've personally given or received.