https://manuel-woelker.github.io/blog/posts/Recent content in Posts on Manuel WoelkerHugo -- 0.146.0en-usThu, 26 Feb 2026 18:00:00 +0100https://manuel-woelker.github.io/blog/posts/2026-02-26-i-wish-i-had-a-language-that-lets-me-prevent-certain-effects/Thu, 26 Feb 2026 18:00:00 +0100https://manuel-woelker.github.io/blog/posts/2026-02-26-i-wish-i-had-a-language-that-lets-me-prevent-certain-effects/An idea for an effect type system, that allows preventing effectshttps://manuel-woelker.github.io/blog/posts/2026-02-23-i-wish-i-had-a-hot-reloading-compiler/Mon, 23 Feb 2026 06:01:31 +0100https://manuel-woelker.github.io/blog/posts/2026-02-23-i-wish-i-had-a-hot-reloading-compiler/Hypothesis: Compilers should compile and hot-reload code as soon as I save it.https://manuel-woelker.github.io/blog/posts/2026-02-19-lets-write-documentation-driven-by-questions/Thu, 19 Feb 2026 06:10:44 +0100https://manuel-woelker.github.io/blog/posts/2026-02-19-lets-write-documentation-driven-by-questions/Hypothesis: Using questions to drive and shape documentation makes it easier to read and write.https://manuel-woelker.github.io/blog/posts/2026-02-01-lets-put-documentation-where-we-can-find-it/Sun, 01 Feb 2026 06:10:44 +0100https://manuel-woelker.github.io/blog/posts/2026-02-01-lets-put-documentation-where-we-can-find-it/Hypothesis: Putting developer documentation directly into the code should make it easier to find, and easier to keep up to date.