In a team, any change to the development workflow must be paired with the corresponding automation tooling. Without a low enough cost of use, the change is meaningless, because nobody will actually use it. In the previous post we covered how to use a CDN for further frontend/backend separation; this

I have been optimizing a project recently. After mapping out the whole chain, I started improving it step by step and found many points that could be improved. What follows are some thoughts on the development model and the deployment approach. I hope they give you some inspiration. 1. Development Background 1.

1. Installing node-sass When installing node-sass, the node scripts/install stage downloads a .node file from github.com, and network problems often cause this to fail. You can add an .npmrc file inside the project to configure a proxy for the installation: 1 2 sass_binary_site=https://npm.taobao.org/mirrors/node-sass/ registry=https://registry.npm.taobao.org Or install with cnpm: 1 2 npm install -g cnpm --registry=https://registry.

Earlier we mentioned that Jupyter Notebook is an interactive notebook that supports running more than 40 programming languages and is very well suited to teaching. Recently, while learning the Go language, I thought of Jupyter. This article mainly describes how to install the Python3 and Go kernels inside Jupyter. 1.

Fruit Ninja Newton’s Cradle Talking Tom