paedubucher

That's why I started using a second phone just for the Google Authenticator App at the workplace. If your authentication does not rely on SMS, you don't even need a SIM card.

Scott Adams describes a possible solution in "Loserthink" (there's probably a longer section on this in one of his other books: "How to Fail at Almost Anything...").

It's called "wiggle your pinky". If you're on the couch and cannot get up, just try to wiggle your pinky. If you have enough willpower for that, move your arm. Then move your legs, put your feet on the floor, and you're already halfway through getting up.

The same with a difficoult (programming) task. Just open the file in the text editor, without having the intention to actually do something. Then scroll a bit through the code. Something might catch your interest. After a minute, you're already in the middle of the task.

Summarized: Just do the tiniest step into the direction of your goal, without the intention of actually doing anything to reach that goal.

Exploring an API?

I always wonder why some many developers work with Postman (or Postwoman), and so without any automation whatsoever. Example: Requesting some JSON payload and extracting some generated id from it looks like a clumsy point-and-click adventure. With curl, you can use any appropriate program to extract output, say jq:

    curl acme.org/my/resource | jq -r '.id'

I see how some project manager doing a presentation of a bleeding-edge feature might profit from Postman, but as a developer?

How (and when) does a Draft Design become a Proposal to be discussed officially on GitHub?

I'm reading Pieter Hintjens "Social Architecture" at the moment, and there he warns exactly about what just happened to Elasticsearch.

That wasn't me, by the way.