ritoune | 4 years ago | on: NCC Group’s Cryptopals Guided Tour
ritoune's comments
ritoune | 4 years ago | on: Dask – A flexible library for parallel computing in Python
Dask, on the other hand, works some of the time. The rest of the time it'll keep running a calculation forever, or simply fail silently over and over, or some other unpleasant outcome.
ritoune | 4 years ago | on: Reflow, a language for distributed, incremental data processing in the cloud
ritoune | 7 years ago | on: Ask HN: Machine learning contractors, how much do you charge hourly?
ritoune | 7 years ago | on: Ask HN: Physicists of HN, what are you working on these days?
ritoune | 7 years ago | on: Why Julia
I would also argue that the large open source Julia packages are also great examples of Julia "in prod".
Just highlighting what I think is a significant con in a language with many pros!
ritoune | 7 years ago | on: Why Julia
When you start building out a project, it's easy to keep track and debug if multiple dispatch starts failing (i.e. <any> type starts spreading everywhere and Julia slows to Python like speeds).
In medium-to-large projects, it becomes extremely cumbersome to manage this. It's doable, but adds a layer of complexity management to projects that simply doesn't exist in strictly typed or pure scripting languages.
Of course, you can just decide to explicitly type everything - but the issue here again is the lack of enforcement.
In a nutshell: Julia is great when you're a grad student working mostly by yourself on small scale projects! But not so great in prod.
And there's really no problem with that; that's who the language was designed for!
ritoune | 7 years ago | on: PyTorch 1.0 is out
Anyone want to start working on Golang bindings for C++ PyTorch?
ritoune | 7 years ago | on: How I Transitioned from Physics Academia to the ML Industry
ritoune | 7 years ago | on: Ask HN: What things have richly rewarded the time invested in mastering them?
ritoune | 7 years ago | on: Ask HN: Why did your startup fail and what did you learn?
He promised meetings with execs and experts in the sector, and expert advice. We split equity 50/50. After three months, we had an MVP that customers loved, a contract with a large client, and several interested angels.
Unfortunately the co-founder hadn't delivered on anything (all business meetings were from cold calls, I had to learn all domain expertise on my own, my co-founder was spending no time at all on the company and kept promising to do things that he didn't end up doing).
After trying to get him to execute what he said he would do with a positive attitude for three months, he called me and told me he "didn't want me to make him feel like he wasn't doing enough". If he was a stranger I would have found a way to kick him out. But to preserve family relationships we killed the company.
TLDR: people in your family with great jobs don't make for good co-founders
ritoune | 8 years ago | on: Firebase Crashlytics graduates from beta