michael_leachim

We are going to have massive shift towards rejuvenation. That is the thing that everybody wants including countries as a whole.

Who wouldn't want to reverse aging and almost fix most of the disease and costs associated with it on their population. Who, on individual level, wouldn't want to look 20 again.

Right now, the problem seems to be that we, in general, we do not believe that such thing is possible.

This will change as soon as we have a robust rejuvenation event at least in mice. After that, the rejuvenation is going to be the new field where all the investors money will go.

On a more modest perspective, stuff related to health and longevity will also see growth. New sensors, new ways to gradually improve health using tech.

My everyday living today is waiting for the war to end.

Electricity cut offs, freezing cold, water shortage, rocket terror and general unpredictability make it harder for me to commit to some sort of a long term plan, much less muster enough energy to do Leetcode style interviewing.

Although, I've started running for an hour per day, which helps with bad mood and suicidal thoughts.

My goals for 2023 and beyond are: survive, connect with people like me, transition, hopefully find a new tech job, get into health/longevity. I believe that logevity is the next big thing.

look at it this way, electricity/flying/computers/space stations were at a time as impossible as rejuvenation now. There is not much difference, just a lot of things to figure out. I think we will get there.

I can't think of anything but longevity/rejuvenation research.

For now, the idea seems far fetched but if it starts to become promising, let's say if scientists will be able to rejuvenate a mouse in a lab, then there are a lot and I mean a lot money to be made.

Every government in the world will be interested in making populace young again, we, as a species are not getting younger through childbirth, hence making population young is going to be a primary goal of policy makers.

The consensus opinion now is that this is not possible, but in reality, I think the consensus is about to change.

When that happens, there is going to be a ton of work in the field and a ton of investment money

Several things that I am working with now:

1) Doing what is difficult. (Started commenting on here, planning to share some of my work here and on Reddit).

2) Asking myself whether I am doing the right thing or avoiding it. (That is when you can spend 3 months in refactoring when you really should just make a landing and share the thing everywhere gathering feedback and iterating along the way)

3) Constant exposure. I am planning to take some work in sales (which I dread). That should help with breaking barriers.

4) Observing the mind. A form of mindfulness approach that warrants its own larger explanation.

Now, I am nearly at the beginning of this journey, but I think I will be able to figure it all out.

Hope this helps.

I am in a somewhat similar position, although I can't say that I have a solid career. I've started through working on a startup and then miserably failed, wasting three years.

Then worked for a small company making money saving and useful services for them, but nothing extraordinary.

Then I tried again. And I failed again. I was disciplined. I planned and worked hard for half a year, having nothing to show for it in the end. To the point, when I just sat and said that I won't do anything code related until I understand where I lack understanding.

I've come to understand that my main problem is fear. Fear of rejection of things that I do. Fear that anything that I can share is of not enough quality to be shareable. Fear of being not appropriate to the people online, or expressing opinions that I have no right to express.

So, now I am working directly with fear. Will see where it will lead me.

The way I see it, there are several reasons for such an interview process:

1) [Leverage]. The interviewer can negotiate down salary expectations based on the performance of the interview. You can ramp up requirements until the candidate breaks. Then, you get the upper hand in the negotiation process.

2) [Responsibility]. Nobody wants to take responsibility for the bad decision. In the formalized interview you can blame the metric. If the metric is external (Google/Facebook/Amazon do it), then there is nobody to assign the blame, so, no responsibility gets redistributed.

3) [Effort]. Treating people as they are different is hard. Reading their CV or learning more about their projects requires time effort and expertise in the field. This is expensive. Much easier is assessing people through a generic process.

4) [Loyality]. Someone, who spends their free time for a year preparing for the interview is bound to be more loyal than somebody who prepares only for a week.

5) [Initiation]. People who go through a difficult initiation process tend to value their group more. That builds tightly knit teams.

Overall, I think that the process is difficult, somewhat irrational and inhumane. But I have no idea how to really fix it.

I use prefix qq for my commands because:

  1. It is easy to discover all customizations 
     via autocomplete
  2. It is not going to clash 
     with existing functionality

  # (Sort stuff by size, latest down, in a directory)
  alias qqsize="ls -lSrh"
  alias qqdate="ls -lrt"
  
  # First 100 of largest files/directories in a folder
  function qqlargest_files_100(){
    du -a ./ | sort -n -r | head -n 100
  }
  
  # Archivate item 
  qq-tar-gz-it () {
    tar -zcvf  $2 $1;
  }
  
  # Convert video to a gif
  function qq_convert_video_to_gif(){
    ffmpeg -i $1 $1.gif  
  }
  
  # Push to GitHub
  
  function togithub__master(){
      git add -A;
      git commit -m $1;
      git push github master;
  }
  
  # Symlink config file
  # 1. Move dotfile to a config directory.
  # 2. Strip the dot
  # 3. Symlink that file back to its place
  function qqsymlink_config_file(){
      directory_for_dot_file=$2
      name_of_dot_file=$1
      basename_of_dotfile=$(basename $name_of_dot_file)
      echo "Basename of dotfile: $basename_of_dotfile"
      dot_file_with_striped_dot=${basename_of_dotfile:1}
      new_file_path=$directory_for_dot_file/$dot_file_with_striped_dot
      echo "Moving $name_of_dot_file to $new_file_path";
      mv $name_of_dot_file $new_file_path;
      echo "Symlinking file $new_file_path to $name_of_dot_file ";
      ln -s $new_file_path  $name_of_dot_file;
  }
  
  # Enable touchpad
  function qq__touchpad_enable(){
      xinput set-prop $(xinput | grep Touch | grep -Po 'id=\K[0-9]+')  "Device Enabled" 1
  }
  
  # Set monitor highlighting 
  alias qq_set_higlighting_to_level_1_100="sudo xbacklight -set"
  
  # Display wifi SSID's
  alias qqwifi-spots="sudo iwlist scan | grep ESSID"
  
  # Add wifi network 
  function qqadd-wifi-network(){
      ## add-wifi-network just_wifi mypassword
      wpa_passphrase $1 $2 >> /etc/wpa_supplicant/wpa_supplicant.conf
  }
  
  # Various, misc
  
  # Mirror (webcam)
  alias mirror="vlc v4l2:///dev/video0"
  
  # Stopwatch/countdown
  function stopwatch(){
    date1=`date +%s`; 
     while true; do 
      echo -ne "$(date -u --date @$((`date +%s` - $date1)) +%H:%M:%S)\r"; 
      sleep 0.1
     done
  }
  
  function countdown(){
     date1=$((`date +%s` + $1)); 
     while [ "$date1" -ge `date +%s` ]; do 
       echo -ne "$(date -u --date @$(($date1 - `date +%s`)) +%H:%M:%S)\r";
       sleep 0.1
     done
  }
  

Some other stuff that I use daily and is too long to list here is:

  * an increment, deduplicating backup that takes
    around $0.52 per month on BackBlaze and on the 
    external hard drive via one command. 
    (Shameless plug: https://github.com/MichaelLeachim/borg_backblaze_backup)
  * Internet blocker.  (https://github.com/MichaelLeachim/internet_block)

Edit, formatting.

That feeling is false. No one is safe from sudden illness and death of themselves and their loved ones.

Access to medicine can help, but it is not going to eliminate the problem.

My main problem with the web usage is not blocking unwanted websites but rather understanding which when and how I should or shouldn't block them.

For example, On one hand, I can't block Wikipedia Stack Overflow or GitHub because I need them for work. On the other, I find myself hours later browsing the source of a project unrelated to the task at hand.

By far, the only way I found to work is to introduce a delay between the need for information and the actual retrieval.

Like you write down queries to the Google and then do something else. In ten minutes time, you do exactly what you wrote in your log file. If you want to search for something else, you introduce it into the journal again, and in ten minutes repeat it. So goes the cycle.

But then, because you have this lag you can't do research faster because your every step is now bound by drag and red tape that you introduced yourself.

TBH, this is a book material here, because working with internet but not abusing the information hoarding instincts is a methodology question.

Not a technical one.

1. Will click on anything with the number of comments more than 100. 2. Then will read the first couple of comments 3. Then will decide whether to read the original article