Fredrik's Homepage

After reporting over 32 000 IP addresses for trying to hack my box, I decided to finally just shut off port 22, and migrate to Tailscale.

Less than half a year ago I was not only skeptical towards AI in my field, software development, but also not very impressed by the results it produced at the time. Now, however, I rarely write code myself anymore, and I'm not really observing the problems I envisioned would arise by the increased use. But. Some concerns I had, I still have.

As a fan, and user, of Kagi, I decided to give their browser Orion a try as my daily driver, only to want to tear my hair out after under two days of use.

I'd love to read more tech blogs, interesting tweets/mastodon-posts, or other programming content, but the massive influx of AI slop and AI hype content takes the joy out of it.

Discussing how you can use the type system to your advantage to avoid passing around values that don't make sense. How types alone aren't enough to ensure your value is "valid", and response to my previous post's feedback on Reddit.

After working as a JS/TS developer for quite some years I've grown quite used to seeing || "" or ?? "" strewn around codebases as a quick fix to "remove" nullability, usually due to some value which you assume is set, but can't "prove" type-wise. I think this is a code smell, and I generally think it's not the right solution. In this post I try to explain why I don't think so, and provide some patterns that could help combat the downsides introduced by this pattern.

My experience using the Zed editor, why I'm struggling to adopt it as my full-time editor, and what I love about it.

An introduction to my new website. Quick explanation of the different technologies used, and my goals for the site. How I've used (and more importantly, not used) AI.