• 0 Posts
  • 93 Comments
Joined 2 years ago
cake
Cake day: July 26th, 2023

help-circle






  • I had similar frustrations with contemporary science in other fields too recently, for slightly different reasons.

    In my case, I was frustrated with all of the studies related to life on Mars where no matter what data scientists crunch, rocks they look at, and gases they sample, the only indisputably meaningful study with a conclusive outcome about whether Mars contains life will be one looking at microbes with a microscope on a rover. Any other study will only amount to weasel words that decisively conclude nothing other than that they collected data points, and the data points look like “this” that “maybe mean something, but more studies are required”.

    I could interview college students about their favorite ice cream flavor, come up with fun statistics, and conjecture about why the data looks the way it does. And at the end of the day, I would have no conclusion beyond exactly what my study’s data is. But the point of science is to advance useful knowledge. Knowledge is what allows us to predict the future, to make informed choices, to avoid guesswork. Raw data is not knowledge.

    Let me repeat this again: DATA IS NOT KNOWLEDGE.









  • I’ve gone through Visual Studio, JetBrains IDEs, Vim, Atom, Sublime, VSCode, probably others too, but frankly VSCode’s simplicity out of the box coupled with great plugin support is hard to beat. Folks who complain about VSCode not having some feature like to ignore that being relatively simple by default is a good thing. You can always add or enable what extensions you need to tailor it to your language and workflow of choice. Even if you’re used to Vim keyboard centric editing…guess what? There’s a well supported OSS extension to give you that functionality.

    The power of being able to use one IDE on a diverse team across various languages is huge. You can even commit extension and settings defaults to a repo to immediately get new cloners up to speed with whatever workflow and tooling defaults are good starting points on a per project basis, but still leaving them the option to ignore/override as needed without dictating a team-wide workflow change.