When working on an app that receives requests from the internet you must have a tunnel to expose your developer machine. Several solutions already exist and work fine most of the time. They do have some drawbacks though. Learn how to create a robust tunnel to your machine without spending a lot of money.
We use OAuth 2.0 to access your information from GitHub. That way we don't have to store any sensitive data and you don't need an extra account. In production this works great. During development it makes our lives harder because GitHub needs access to our machines. We solve this problem by mocking all OAuth related networks requests to generate a fake token. This token won't give you access to the GitHub API so we also have to stub those requests.
Lighthouse is great during development for auditing performance metrics. Using it in Continuous Integration is a little more tricky but easier than you might think. Learn how to automatically keep an eye on the indicators Performance, Accessibility, Best Practices, SEO and PWA.
Creating code coverage for your React application is easy. We are using create-react-app to set up our project and with the help of a few little scripts we are able to monitor code coverage while building our final product.
We added support for badges as our latest feature. We all love those little SVG images within our repositories. You are now able to create a badge for every single series. Let your users know about your key performance indicators.
Usually you keep your dependencies out of your git repository. It is a widely accepted approach and has several advantages. We would like to convince you that checking all your dependencies into version control is a great idea.
Getting started with Docker is super easy. However it is also easy to shoot yourself in the foot. Default Docker images are quite large and since you need a lot of them it all adds up. Keep an eye on your Docker image size by using four simple techniques.
Having benchmarks for your critical code paths ensures stable performance and protection against accidental changes. However benchmarks are usually only done once and never run continuously. Learn how to keep an eye on your benchmarks over time.
Code coverage is a first class citizen in Go. However programmatically getting the total code coverage for multiple packages within a single project can be tricky. Learn how to retrieve the overall code coverage by using standard Unix command line tools like grep and awk connected via pipes.