Jonas Pauthier Nargonath

Name	Website	Access	Data Import (API/CSV)	Trading Charts	Login Required	Transactions, P&L	Coin Location	Tax Advisor	Social Features	Alerts	Price	Notes
Blockfolio	http://blockfolio.com/	Mobile-only (Android, iOS)	No	Yes	No*	Yes	Yes*	No	No	No	Free	Desktop app "coming soon"
Delta	https://getdelta.io/	Mac Desktop, iOS, Android	No	Yes	No	Yes	Yes*	No	No	Yes	Free + Upgrade ($)	Nice modern UI. Desktop app available as of March 2018
Lionshare	https://lionshare.capital/	Mac Desktop & iOS	No	No	No	No	No	No	No	No	Free, OSS
CryptoCompare	http://cryptocompare.com/	Web App	No?	Yes	Yes	Yes	Yes*	No	Yes	No	Free	Portfolio is one part of a far larger community app
AltPocket	h

Eric Elliott's "Master the JavaScript Interview" Series

A collection of links to the "Master the JavaScript Interview" series of medium stories by Eric Elliott.

Not part of the series but a good grounding.

Master the JavaScript Interview

Vim without NERD tree or CtrlP

I used to use NERD tree for quite a while, then switched to CtrlP for something a little more lightweight. My setup now includes zero file browser or tree view, and instead uses native Vim fuzzy search and auto-directory switching.

Fuzzy Search

There is a super sweet feature in Vim whereby you can fuzzy find your files using **/*, e.g.:

:vs **/*<partial file name><Tab>

React lifecycle cheatsheet

Method	Side effects¹	State updates²	Example uses
Mounting
`componentWillMount`		✓	Constructor equivalent for `createClass`
`render`			Create and return element(s)
`componentDidMount`	✓	✓	DOM manipulations, network requests, etc.
Updating
`componentWillReceiveProps`		✓	Update `state` based on changed `props`

How to use cozy cloud in a persistent way with docker.

First, simply creating a docker container with cozy running in it can be done this way.

dockrer run -d --restart=always --name cozy -p 6500:443 cozy/full

-d makes it run in background (you can remove it to see the logs at startup, but you can also use docker logs cozy to see them either way).

--restart=always means that if the docker service is restarted, or even the server, the container will be restarted right away, making for less maintainance for you.

If you have a package where a lot of people are still using a legacy version of it you might want to keep pushing (security-)fixes to that "branch".

Let's say the "latest" version of your package is "5.4.0", but there is as significant amount of people still using "4.7.4" – the last version you released before doing "5.0.0".

You found a critical bug in "5.4.0" and push it as out as "5.4.1", but it applies to "4.7.4" as well and so you want to do "4.7.5".

Assuming you have semantic-release already set up, you can follow these steps to get that "4.7.5" legacy support release out.

Go to the relevant commit: git checkout v4.7.4
Create a new branch from it: git checkout -b 4.x (You can choose any branch name, just make sure to use the same in step 3)

	#!/usr/bin/env bash

	branch=$(git symbolic-ref --short HEAD)
	version=$1

	if ! [[ $branch =~ ^flavor- ]]; then
	echo "Not on a flavor branch" >&2
	exit 1
	fi