anjakefala

I think the argument is that for non-scientific usecases, folks don't really need to think about error or significant digits. By focusing on the significand too much laypeople aren't grasping how large and small these numbers are relative to each other.

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.

If you subscribe to the newletter here: https://hanukkah.bluebird.sh/about/ =) You'll here about our next datagame.

Click on the candles to see the puzzle! Start with the 0th candle in the centre. =)

Yes, exactly! A new puzzle will be released at 4pm UTC each day.

Would you be open to filing an issue with these details? https://github.com/saulpw/visidata/issues/new?assignees=&lab...

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.

For example, some apparently 10x engineers were only so because they were allowed to only work on interesting, relatively easy early stage work. The difficult, fiddly work of mopping up the awkward corners was left to other engineers, who were considered 'slow'.

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 recommend this tutorial! =) https://jsvine.github.io/intro-to-visidata/the-big-picture/v...

Do you have a link to the tool you built with vdtui? =)

They substituted veggie soup cubes with chicken ones.

I am a vegetarian. :/

++ for checking that you were using the correct pronoun for the author!

We would also welcome you with open arms at https://github.com/saulpw/visidata =) Send us an email, or join us on freenode, twitter, etc, if you want to help out! I would love to onboard you.

If you pipe your output into VisiData[1], it will structure fixed width text for you into a tabular form. =)

Just type `blah | vd -f fixed`

[1] http://visidata.org/

  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

Open-source tool for quickly opening and exploring tabular data: https://jsvine.github.io/intro-to-visidata/index.html

(Disclaimer: I build homebrew, apt, etc packages for VisiData.)

I feel like this is the core of how "Open Software" is aiming to combat this. By removing the consumer-driven model away from software and putting users in closer touch with developers, we are supposedly developing tools together that better fit our needs. Though, OSS arguably is struggling to meet this theoretical ideal, especially with the current lack of support most OSS devs have.

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.

I found this to be a very clear and well-structured post. I was not surprised to read that the author is a historian. I especially liked the detail in their process where they automatically update the communal sheet to indicate that the data has already been processed.