It's not being put forward as a recommended tool for scientists when reasoning about precise values. It's put forward for laypeople when trying to understand the vastness of the universe.
108 karma · joined October 28, 2017
It's not being put forward as a recommended tool for scientists when reasoning about precise values. It's put forward for laypeople when trying to understand the vastness of the universe.
We do not have anyone who is deeply familiar with USV spec details on the team, and could use your help to understand what needs to be fixed.
I am someone who loves mopping up the awkward corner cases. For me, this is the most fun part of coding. I think the early design and infrastructure work is actually pretty challenging work. The decisions made at this stage pay dividends later on, in ease of debugging, api goodness, future expendability, etc. I prefer collaborating with senior engineers who are strong and relatively fast with that, and then I help clean-up to facilitate their speed. If everyone is on-board, I am not sure what is wrong with this arrangement.
I am a vegetarian. :/
Just type `blah | vd -f fixed`
Location preference: Vancouver, Canada
Remote: Open to
Willing to relocate: To the US
Technologies: Python, Bash, R, statistics, strong linux foundation, some exposure to AWS, experience with medical imaging technology and protocols - interested in devops/sre
Résumé/CV: http://anja.kefala.info/resume.pdf
Email: anja.kefala@gmail.com(Disclaimer: I build homebrew, apt, etc packages for VisiData.)
My life improved considerably when I switched from Sublime to vim, Excel to VisiData, Word to LaTeX (though, I am unsure if LaTeX is completely OSS), etc. I invested the time in learning the language of the tool, but it pays off in droves.