So I've been trying to set access to my CMS for a long time now. The problem was that in order to have CMS accessible through my domain, it requires an OAuth server. I've figured out that creating a custom serverless function which will handle the authentication with GitHub would be sufficient.
Technical debt is a massive problem that costs a lot of time for everyone working on the team. It should be part of the development cycle to eliminate it.
Last week I'd organized a small briefing at work about WebAssembly. The goal of the briefing was to give my colleagues an overview about what WebAssembly is and how it can be used to improve our products. I've used these notes for the discussion.
I was thinking of the ways how could people subscribe to the blog without checking it periodically or me having to post on social media any time that I post a new article. The first thing that came to my mind was an RSS feed. I thought that it should be very easy to create one (and it is) so I started to work on it last weekend.
I was very sceptical of the new trend of truly wireless headphones at first. I didn't believe that the technology is capable of producing a high quality headphones with a sensible time of usage without some major drawbacks in comfort of wearing them or some other major issues.
So it has been 3 months since I've made a full transition to only writing on Colemak keyboard layout. Now that I am in the middle of the adaptation period is time to sum up what was causing the most problems and what went smoothly. Lazy explanation would be that it is something between QWERTY and Dvorak. It keeps the most used shortcuts unchanged and moves the keys that are most frequently used to the middle.
In this blog post, I am going to take you out on a little journey of making my own keyboard. Perhaps help you if you've decided to make yourself your own. But first, I want to tell you: