I think that walks in nature work significantly more often, but the effect is short term lasting days instead of months or years. Also, walking once or more a week is helpful long term.
175 karma · joined March 9, 2014
I think that walks in nature work significantly more often, but the effect is short term lasting days instead of months or years. Also, walking once or more a week is helpful long term.
(It's not focused on Monoids. It also covers groups, rings, and fields from a mathematical point of view. It's written for an undergraduate math major with no prior experience in these areas.)
I lost my enjoyment for programming. I wrote very little code for about 5 years after burning out. One of my friends wanted to do a joint coding project and he suggested Haskell, so I solved one or two hundred project Euler problems in Haskell. I never got good at Haskell, but I really do enjoy writing smaller projects (less than 5,000 lines of code) in Haskell.
Haskell inspired me to read two fairly easy books on Category Theory. I really enjoyed that also.
I still don't write a lot of code. Every few months, there will be a problem at work that needs my help and then I write the equivalent of 3000 lines of C++. Or, there will be a math problem that I want to solve on the computer. I really enjoy writing those shorter, self-contained programs.
(PS: I started writing code in 1980.)
Date Cases New Cases
March 10 9172 1797
March 11 10149 977
March 12 12462 2313
March 13 15113 2651
March 14 17660 2547
March 15 21157 3497
March 16 24747 3590
March 17 27980 3233
March 18 31506 3526
March 19 35713 4207
March 20 41035 5322
March 21 47021 5986
March 22 53578 6557
March 23 59138 5560
March 24 63927 4789
March 25 69176 5249
March 26 74386 5210We also made crystal diode radios, but I have no idea how to construct a diode from scratch, so maybe those are not simple.
Suppose that you have a 2 planet system: A sun type star (mass 210^30 kg), an Earth type planet 1 AU from the sun (weight 610^24 kg), and a Jupiter type planet (mass 2*10^27 kg) that is 1000 AU away from the sun.
The distance between the Earth type planet the center of the star could be nearly constant.
The distance between the Earth type planet and the barycenter would not be nearly constant -- it would not "orbit" the barycenter in a circular orbit.
I may be wrong and I would be very happy if someone corrected me.
(Note: I think the barycenter would be about 5 AU from the star!)
I believe that the statement is a good approximation for the orbits of trans-Neptunian objects or any other orbiting object that is more than 40 AU from the Sun, but I think it is a bad approximation for Mercury, and not a good approximation for the Earth. When I say it's a bad approximation, I mean that it would be more accurate to say "the Earth and Mercury orbit the center of the Sun" than it is to say "the Earth and Mercury orbit the barycenter of the Solar System (center of mass)".
Any comments by someone more qualified that me would be appreciated (I took about 6 courses in physics and 2 courses in astronomy in college and I graduated over 20 years ago).
The time to compute sqrt(5) was 0.23 sec. The time compute the formula (I dropped the insignificant 1-sqrt(5) term) was 2.8 seconds. When I used the built in Mathematica function to compute the Fibonacci number, it took 0.12 seconds.
A lot of it depends on the complexity of the software and the complexity of the interface to the user(s). If the software merely needs to do something simple like accounting, I think a mechanical system could be made, especially one that processes punch cards (see Vaylian's answer). Mechanical systems usually require some maintenance, but if you made many copies of the mechanical system and many copies of the documentation, then you could probably still run it in 100 years on one of the mechanical computers.
If the software is an unchanging, complex, but it has a simple interface (like terminal standard input/output ascii), then consider: 1) writing the software in an old language like C or Lisp, 2) compiling the software into a Turing machine, and 3) writing a program in Fortran, C, or Lisp that can run the Turing machine quickly. (In particular the implementation should make memory access a constant time operation.)
If the interface is complex, like the internet, or graphical, then you are pretty much hosed. Somebody is going to have to maintain the interface, but you could still use the Turing Machine idea to implement the logic that is not tied to the interface. As Patio11 said, your #1 problem is "making an organization which persists for 100 years." I suggest finding an organization that has lasted 100 years and making one person responsible for the software with the idea that he/she will maintain the software/hardware for at least 40 years and then pass along the responsibility to someone else. You would need some good contracts to make this happen, but it is not too unusual for a teacher to teach in the same high school for 40 years, so you could probably design the contracts accordingly.
You should probably write the documentation in English and put it on acid free paper.
The bottom lines are: 1) Compile into a very very simple language, 2) Implement on very simple hardware (Onion2k), and 3) Set up a human organization (Patio11) as simple as possible with good contracts that will last 100 years.