Hi!
I started a blog recently, and one of my recent discussions on FFT led me to post a new blog post at https://nor-blog.codeberg.page/posts/2024-06-01-implementing-fft/ exploring some FFT algorithms — more specifically, alternate (potentially better) implementations that not many people are aware of. The contents of this post might be a bit well-known to people who write their own FFT templates, but having a good understanding of FFT should help others too.
Why a new blog? - Not all of what I have written/plan on writing is directly related to competitive programming, and I like keeping my content organized in one place.
- I'm trying to follow a tagging system (and it's pretty nice, click on any of the tags here to find a list of relevant posts, as well as get an RSS feed for each tag).
- Codeforces search is pretty lacking, I tried to make up for it by making my blog searchable, and I'd say it works well enough for most purposes.
- Native dark mode!
- Codeforces does not have a RSS feed, and I feel they improve quality of life significantly. I strongly recommend considering using them. Along that line of thought, my blog has a RSS feed too. I recommend subscribing to it, since I would generally not be cross-posting new posts to CF.
- There's generally a lower amount of noise on self-hosted content.
- It's much easier for me to set up and post to, while also keeping track of what I've written in the past. I use Doom Emacs + Org Mode and it's amazing.
- Finally, Codeforces terms require you to give certain rights to your content to Codeforces, something I don't feel very good about. If Codeforces decides to wind down its operations, most content that the community has painstakingly produced can be lost in the blink of an eye, and the terms allow this. IMHO, it's better to have local backups of your own content. I'll try to keep my posts synced on the Wayback Machine from time to time, in case I decide to stop hosting my own blog, though that is pretty unlikely.
Full text and comments »