Implementing vs understanding vs using
The benefits and pitfals of implementing too much yourself.
Brain dumps, evaluations of projects and setup guides.
I don't expect anyone to read these, but if you do, I hope you find them useful. These are written because it helps me understand things better myself, and for when I need to recall something e.g. my workspace setup.
Why everyone should dabble with low level tech, but 99% of web dev people should stay away after.
First of all, I am no expert on any low level technologies. I have played around with C. I have never used C. I Fell in love with Rust. I have never used Rust. They give you a fantastic understanding of what is going on behind our runtimes, web servers and programming languages; but simply said, only very few people have to bother.
My neovim IDE environment for web development
Tired of the performance of VSCode? Always wanted to feel like a hacker working in the terminal? Tired of using your mouse giving you RSI? The command line is not just for low level coders or quick adjustments of files on the server. With a bit of practice, and the right setup, you might never look back.
Refactoring considerations
In this article I will talk about my experiences with refactoring projects. For this project I will give examples of a project I have been working on from the start of my career as a developer; where the following two considerations will continuously return, as motivation to refactor the project code
The T3 stack
When we released the first version of cosmOS last year, it was written in Go. Go is a wonderful programming language, but it’s been a while since I’ve seen an article on the front page of Hacker News about rewriting some important tool in Go and I see articles on there about rewriting things in Rust every single week.