• 0 Posts
  • 68 Comments
Joined 1 year ago
cake
Cake day: July 10th, 2023

help-circle





  • nfh@lemmy.worldtoScience Memes@mander.xyzEat lead
    link
    fedilink
    English
    arrow-up
    78
    arrow-down
    1
    ·
    25 days ago

    We can’t prove that the world we live in wasn’t created last Thursday, with our memories, the growth rings in trees, and so on created by a (near) omnipotent trickster to deceive us. But science and rationality give us tools for determining what’s worth taking seriously, and sorting out the reasonable, but unconfirmed, claims from the unverifiable hogwash.


  • nfh@lemmy.worldtoScience Memes@mander.xyzThe 1900s
    link
    fedilink
    English
    arrow-up
    7
    ·
    1 month ago

    And even then it’s probably not a hard rule as much as a good heuristic: the older a source is, the more careful you should be citing it as an example of current understanding, especially in a discipline with a lot of ongoing research.

    If somebody did good analysis, but had incomplete data years ago, you can extend it with better data today. Maybe the ways some people in a discipline in the past can shed light on current debates. There are definitely potential reasons to cite older materials that generalize well to many subjects.


  • Knowledge is what happens when you’ve evaluated enough evidence to reject the null hypothesis that something is false. If you haven’t seen the evidence, but still think it’s true or false (you don’t lack belief), then you have a belief about it. As such, knowledge is a type of belief with extra justification.

    If I’ve reviewed enough evidence I’m comfortable saying I can reject the null hypothesis, that is I have a belief that it’s knowledge, I’ll call it as such. If I haven’t, I’ll couch my confidence in my belief accordingly.









    1. I’ve learned a number of tools I’d never used before, and refreshed my skills from when I used to be a sysadmin back in college. I can also do things other people don’t loudly recommend, but fit my style (Proxmox + Puppet for VMs), which is nice. If you have the right skills, it’s arbitrarily flexible.

    2. What electricity costs in my area. $0.32/KWh at the wrong time of day. Pricier hardware could have saved me money in the long run. Bigger drives could also mean fewer, and thus less power consumption.

    3. Google, selfhosting communities like this one, and tutorial-oriented YouTubers like NetworkChuck. Get ideas from people, learn enough to make it happen, then tweak it so you understand it. Repeat, and you’ll eventually know a lot.


  • It’s a question of the most stable thing to use to mediate value for exchange of goods and services, right? Fiat currency is just the choice of “the state” as a stabilizing force. Certainly it’s better than trusting the scarcity of rare metals, but eventually “just trust the state” will become a problem, and we’ll need to think about rebasing currencies. In theory, computational complexity isn’t a bad choice, but nobody has come up with a solution that actually functions well as a currency.

    But I agree, the finite planet has nothing to do with any failings of fiat currencies, and only makes sense as a failing of the “number must go up” mentality endemic to capitalism.



  • I don’t think anyone intends public funds to be quite that sticky; public education is itself a public good, and having once attended a public school really has nothing to do with developing a product 20 years down the road.

    Also, writing open source code can support a viable business. Not every example has been successful, and some have been sold to hypercapitalist owners who wanted to extract more profit, others have failed to keep up, but Canonical is doing alright with it, Red Hat did for a long time, among others. Plenty of bigger tech companies also employ people to write open source software, despite it not being the company’s main business, React, PyTorch, TensorFlow, and so many other projects. Those engineers definitely aren’t working for free.