• 0 Posts
  • 52 Comments
Joined 1 year ago
cake
Cake day: August 8th, 2023

help-circle


  • My personal tale on this is that given that the brain contains chaotic circuits (i.e. circuits in which tiny perturbations lead to cascading effects), and these circuits are complex and sensitive enough, the brain may be inherently unpredictable due to quantum fluctuations causing non-negligible macroscopic effects.

    I don’t know if the above is the case, but if there’s anything like free will out there, I’m inclined to believe that its origins lie in something like that.



  • In 2020 there were 448 events at the Olympics, let’s round up to 450. Each event gives 3 medals, for a total of 1350 medals. The Olympics are held every four years, so that 337.5 medals are awarded in an average year.

    There are about 8.1 billion people in the world. On average, 0.000004 % of the worlds population receives an Olympic medal each year.

    If this were a completely random yearly lottery, and you lived for 100 years, you would have about a 0.0004 % chance of winning an Olympic medal in your lifetime.

    I would count myself lucky if I won that by the time I was 50.




  • Software is a tool. I develop stuff that i know is of interest to companies working with everything from nuclear energy to hydrogen electrolysis and CO2 storage. I honestly believe I can make a positive contribution to the world by releasing that software under a permissive licence such that companies can freely integrate it into their proprietary production code.

    I’m also very aware that the exact same software is of interest to the petroleum industry and weapons manufacturers, and that I enable them by releasing it under a permissive licence.

    The way I see it, withholding a tool that can help do a lot of good because it can also be used for bad things just doesn’t make much sense. If everybody thinks that way, how can we have positive progress? I don’t think I can think of any more or less fundamental technology that can’t be used for both. The same chemical process that has saved millions from starvation by introducing synthetic fertiliser has taken millions of lives by creating more and better explosives. If you ask those that were bombed, they would probably say they wish it was never invented, while if you ask those that were saved from the brink of starvation they likely praise the heavens for the technology. Today, that same chemical process is a promising candidate for developing zero-emission shipping.

    I guess my point is this: For any sufficiently fundamental technology, it is impossible to foresee the uses it may have in the future. Withholding it because it may cause bad stuff is just holding technological development back, lively preventing just as much good as bad. I choose to focus on the positive impact my work can have.


  • There’s evidence that knights would dismount before battle to prevent their horse from being injured, even though they knew they were exposing themselves to greater risk. Although we have more technical knowledge about how to “optimally” care for horses now, there’s no reason to believe that we aren’t as or more exploitative of them, rendering them as or less healthy than horses back then.



  • I am very fond of the idea of “stateless” code, which may seem strange coming from a person that likes OOP. When I say “stateless”, I am really referring to the fact that no class method should ever have any side-effect. Either it is an explicit set method, or it shouldn’t affect the output from other methods of the object. Objects should be used as convenient ways of storing/manipulating data in predictable/readable ways.

    I’ve seen way too much code where a class has methods which will only work"as expected" if certain other methods have been called first.


  • Sounds reasonable to me: With what I’ve written I don’t think I’ve ever been in a situation like the one you describe, with an algorithm split over several classes. I feel like a major point of OOP is that I can package the data and the methods that operate on it, in a single encapsulated package.

    Whenever I’ve written in C, I’ve just ended up passing a bunch of structs and function pointers around, basically ending up doing “C with classes” all over again…



  • This makes sense to me, thanks! I primarily use Python, C++ and some Fortran, so my typical programs / libraries aren’t really “pure” OOP in that sense.

    What I write is mostly various mathematical models, so as a rule of thumb, I’ll write a class to represent some model, which holds the model parameters and methods to operate on them. If I write generic functions (root solver, integration algorithm, etc.) those won’t be classes, because why would they be?

    It sounds to me like the issue here arises more from an “everything is a nail” type of problem than anything else.