More Readable Tests, Docs, ... [this is a draft]
I used [axios] in a project and while I was reading the docs to learn how multiple interceptors work, I had to dig all the way into the tests and into the source code to finally understand it fully.
I used [axios] in a project and while I was reading the docs to learn how multiple interceptors work, I had to dig all the way into the tests and into the source code to finally understand it fully.
I started learning github actions (and wrote about it). Not true. I was reading about them, trying to understand how they work. I invested one day, after clarifying the terms for me I figured out that I can go as simple as using some actions from the github marketplace and be done. But I prefer to understand what's under the hood. So I did dive in and found that there are multiple repos and more, there is a power behind github actions that seems to go beyond what travis, drone or jenkins offer.
The title does not really enclose all the topics and cover the full value of this talk. Actually it is not explicit enough, because sustainability is a word that is being used in too many contexts and means too much. I would maybe rephrase the title to "The Real Cost and Value of Open Source and Why and How Your Company can Participate and Give Back". A bit clunky, but it tells the story I believe.
Continue reading →
Having a useful and pleasant to read README does sometimes make a difference in deciding to spend more time with a package or project. The tips by James Scott really help, having a template like he provides is actually a really good idea. Thanks.
This is JS (and) Crafting #6 - April 3rd, 2017. Every Monday you will receive a hand-selected collection of links about JavaScript and how to craft better software. Let's get started ...
This is JS (and) Crafting #5 - March 27th, 2017. Every Monday you will receive a hand-selected collection of links about JavaScript and how to craft better software. Let's get started ...