Search for a command to run...
My name is Michael Lehmann. I'm a developer, architect, technical team lead and occasional speaker. I work for Zühlke Engineering AG as a Lead Software Architect aiming to help my customers and team mates to design and develop software. I specialised in developing distributed systems with micro-service architectures and modern web technologies.
No comments yet. Be the first to comment.
15 years ago, C# did not have a large variety of unit test frameworks and supporting libraries. That has changed in the meantime. The community has grown considerably and so has the range of libraries and tools that can be used for unit tests. While ...
If you read my blog regularly you may have noticed that I recently introduced pagination to my article list. In order of that, I would like to explain how I implemented that with the tech stack of my blog - NextJS and MongoDB. Pagination is one of th...
A good friend of mine once told me about a conference talk that was about so-called task-based UIs. I considered this architecture style for an application in a private bank which was responsible for checking the suitability for finance instrument tr...
In larger projects, the cooperation of several teams and long-term maintenance is always an issue. The architecture must be defined in such a way that such aspects are possible. This is often implemented with a certain degree of modularization. This ...
I recently implemented a small hint showing the reading time of an article in my blog. This is a functionality used quite much when reading some technical articles written by the developer community. It helps me to decide whether I have the time to read an article just now or if I'm going to put it on my stack. So I thought it would be nice to provide my readers with the same flexibility.
According to Medium the reading time is based on the average reading speed of an adult (roughly 265 words per minute).
To get a basic implementation of this I could get rid of the Markdown markings and count the words by splitting the string by spaces. Images add additional time to the reading time and this approach would not consider that.
Luckily I found a nice npm package reading-time that does this for me. It can handle plain text, HTML, and markdown.
All I need to do is install the package.
npm install reading-time --save-dev
And use it to convert my markdown content to an estimated reading time
import readingTime, { ReadTimeResults } from 'reading-time';
const result = readingTime(post.content)
The result contains several properties. I can get the text 3 min read by accessing result.text or alternatively the reading time as a time result.time, in minutes result.minutes and the word count result.words.
In the end, it was very simple for me to integrate an estimated reading time into my blog.