Development tips, snippets, and tricks
While I specialize in full-stack development with Microsoft technologies, I also have experience with other technologies. The artilces below are examples of things I’ve learned and found useful.
Fixing bad SSH keys
SSH keys are a great way to authenticate with a remote server. They are secure, and they are easy to use. However, they can be a pain to manage. If you have ever had to deal with a bad SSH key, you know what I mean. Especially if you are using cloud services where IP addresses may be reused.
How to calculate estimated reading time
When publishing an article it is often a nice touch to let users know roughly how long it will take to read, and what level of investment they can expect to make. While every reader is different, the average reader can ingest about 150 - 200 words per minute, depending on the type of text.
Becoming an effective open source maintainer
Developing code is not easy. It is a challenge, but it is also a fun thing to do. Maintaining a project, however, is not easy either. It requires a very different skillset and time investment. When I became a maintainer of Selectize, I was able to learn a lot about the project and how to improve it, and I was able to learn so much about how to interact with the community.
Redirecting pages in jekyll (Without Plugins)
Hosting your site on Github Pages is fantastic, easy and inexpensive. Using Jekyll to generate your pages is easy and very configurable. It’s the perfect solution for a static site (as well as what I use for this blog). Sometimes, however, you may run into situations where you need to redirect a page to another page, and without access to your backend to use server-side redirects you need to do it manually.
How to determine what app is using a port
While it is sometimes easy to determine what app is using a port, it is not always the case. For example, if you are running a web app, and you want to know what app is using port 80, you can’t just look at the process list. You have to run a script to find the culprit. In the past this was a netstat command, but it can be simpler to use PowerShell.