A poor man’s instapaper

I’ve stopped using Instapaper for a long time now, but I’m still reading longreads. Let me explain how.

I go through my links in Chrome on my desktop. I close and read whatever I can and anything that’s too long stays in an open tab and floats slowly to the left.

On Chrome on my phone whenever I’m in transit or when I want to read something longer that isn’t a book, I go to the “Recent tabs” screen. Besides those you can also find synced open tabs from all your other Chrome browsers. I then pick something that I want to read.

Now, ideally it would allow me to close the tab on my desktop from my phone but understandably that’s not a feature. So I read a couple of articles, remember those and close the tabs manually next time I’m back on my desktop.

This works surprisingly well. Except for LRB articles. I have no clue what to do about those.

About password managers:
“But I never found a way to get people onto 1password in a single training session. The setup process has a lot of moving parts, involving the desktop app, browser plugin, online service, mobile app, and app store. It requires repeatedly typing a long master passphrase.”

People do not like to hear it but password managers are BAD. Even the best of them is so bad that I struggle to use it. (I do because I have no alternative.)


Tooling has become so good and so empowering that like in this tweet, many commerce ‘startups’ that are really struggling to hire and retain dev teams (and then utilize them to their potential) would be much better served using Airtable, Zapier and Pipedrive until they break.

More likely in any case that the startup will go out of business or be acquired than it hitting the limits of those kinds of tools.

Set aside all of the obvious outcry, I haven’t seen a single argument yet that explains how encrypted communications are compatible with state power.


I listened to this and didn’t hear that explanation nor did I find many of the arguments against very convincing.


“Changes to one team’s service may be implemented by another team who needs the enhanced capability by what is called an Away Team. This team works on the Home Team’s code to add what it needs according to established engineering standards and then leaves that code in good order to be maintained by the Home Team who owns the service, with help when needed.”

Fully embedding your team in another team’s context to get something done, seems to me a very interesting compromise between autonomy and collaboration. Every team is an island, but it is ok to travel to another island and if that’s not possible, you can still build your own.

Also more than disorienting to see an in-depth piece about engineering organizations like this appear on The Register.

Putting an entire team in another team’s context is something I have considered for all the collaboration, delivery, culture etc. benefits that it will most likely yield in exchange for a minor hit in delivery.