I'm a front-end developer of accessible user interfaces from Leiden, the Netherlands. I currently work in a product team where we create software for mental health providers. I'm a metal, loud and alternative music connoisseur. This is my personal website where I share notes, ideas, thoughts and links.
♫ I recently bought a bunch of CD's on sale. Three albums by Dark Tranquillity that I missed from my collection and come recommended on Rate Your Music. Character is one of the albums and it's indeed a perfect mix of melancholic and melodic death-metal the band has been known for. The songwriting is a highlight, with almost no fillers and crystal clear production. I do miss Mikael's clean vocals this time around. Check it out on Songwhip.
♫ A lot of new music was released this week, but I'm listening to an older album I recently picked up right now. Djevelsvart (2013) by the Norwegian Glittertind. A traditional Scandinavian folk punk, metal hybrid. If Gåte and Kvelertak had a baby. Djevelsvart on Songwhip
As a front-end developer working on a similar type of web application in the mental health care space, Eric Bailey's article about performance of modern front-end frameworks really hit home.
I have to admit, as I assume a lot of other developers are in the same boat: I wasn't involved in setting up the architecture at my company. I'm currently working with a front-end framework that was picked by (non-front-end) developers who choose what aligned best with their coding practices and was similar to what they worked with before.
Do we over-rely on client-side rendered JavaScript? Perhaps we do, and I would love to be able to change this in the future by moving more towards native web API's. But the hardest thing is to convince stakeholders this is a worthy goal pursuing. With a small product team we have a lot of other projects that need attention and take up precious time. Refactoring our relatively young front-end stack might not get a high priority status (or any status at all) in the next few years.
I'm interested in solutions and ideas on how to tackle this problem as an individual developer. We are knee deep into a relatively popular client-side JavaScript framework, written in TypeScript. It's too complex in my opinion, but works fine, is part of an even bigger complex stack and is well-engineered. But I would love to lose the complexity, the potential barriers for our users, and move more towards native web solutions. I just have to figure out how to exactly do this.
♫ It took me a couple of years, but Tribulation finally clicked for me. This is gothic deathrock meets black-metal and they really do their own unique thing. I love the guitar playing on this record. I can't wait to dive further into their discography. Listen to Children of the Night
♫ A new song by The Ocean is always a good thing. I wonder if Pelagic Records mysterious pre-order campaign is for a new The Ocean album. Listen to Preboreal on Bandcamp
I would be great if Apple solved some of the longer lingering bugs in Apple Music on macOS. For instance, (while using Airplay) adding a new song to my queue while the current song is almost ending usually results in the new song playing without sound. Also use the search too much and you're unable to typ more than one character in the search input. If services are becoming more important for Apple, it's disappointing they are really taking their time to fix bugs in Music.