By now there are probably more articles about the flaws of NPM and the NPM registry than articles about how Java will die soon, but I feel like there haven’t been many of them which suggest solutions or workarounds to these problems, so these are the aspects I want to try to focus on in this article.

While the JavaScript ecosystem is often criticized for being too complex and/or having way too many dependencies and tools (and rightfully so most of the time), we should keep in mind that most of them are used for a reason: Linters help you prevent and find bugs, bundlers and minifiers improve performance, etc.
This article tries to highlight tools which you might find useful and might improve your workflow.

With the rise of societies acceptance of trans* and non-binary gender identities,
It’s time to think about how to handle the traditional “Male”, “Female” and “Other” radio buttons of forms, both on paper and in applications and web sites.

Recently I did some research on what exactly the latest standard for the content of the of the head of an HTML document is; Below you can find a detailed breakdown on how the different sections can or should be built.

This is the second part of my series about JavaScript bundling & building. If you haven’t read the first part yet, go check it out, otherwise the content of this part might not make sense to you.