Day 52: Calls explained, avoiding Google

Explaining REST calls, avoiding Google tracking

1 min read    23 Jun 2017    

Check git punchcard later.

Explaining post and put calls, by the book. This happened when explaining Java coder the types of calls. Say I need to write something in a book.

  • For that, the book must exist. So first, I shall buy the book or make one. This is a POST call.
  • Now I want to write down something of importance to me. I put the data in there. A PUT call.
  • Now, to uniquely identify that this is my book and no one else’s, I write my name in it. This can be handled both in a POST or PUT call [preferrably PUT] , as in, I can write my name as soon as I buy it, or later back at home.
  • A friend of mine needs my copy one day before a test. He needs to get it from me so that he knows what to study. This is GET.
  • Eons paas. The book is of no more importance to me, so I shall dispose it. This is the end, DELETE call.

JS code is a fan of Heisenberg’s uncertainity. The more the importance of something to work, the less is it likely to actually work.

Say, m means the mass of importance, and p represents the probability of working, it can be said to a certain level of accuracy that,

m.p >= constant

A week of planning can save you an hour of programming.

Although this sounds stupid, and seems right the other way, this statement, unaltered, makes total sense.

urlparamify update: This was the low point I had

Back at the top:

There are a couple of things you should do if you don’t want anyone to track your data:

  • Throw away gmail
  • Don’t sign in at google chrome
  • Don’t use android. They track EVERYTHING using android.
  • Don’t use facebook
  • Don’t use google.

Why are people so fixated with IIT’s? People who ultimately want to join an IIM want to get to an IIT first.

You can loop between two points in a youtube video by right clicking two points. The highlighted interval turns green.

Some rights reserved.

Leave a Comment