There are a few things in programming that just universally suck and any filesystem code is definitely among that

Trying to write a "reactive" processing pipeline where changes to input files automatically trigger
rebuilding of derivative files, and my god, do I not like this ;_;

At EVERY step you need to think "what is the worst possible race condition that could happen here and how can I prevent that from fucking everything up"

I think the pattern I came to is to be as conservative as possible: Don't ever forget/skip any change events but just accept that we will get multiple events for any change. And not just because the file was written to multiple times per change (which happens a lot!), but also because changes might happen *while* we are updating the derivative resource.

So if you only acknowledge the changed timestamps before running the rebuild and never skip events, then you should at least never have a stale resource, even if you need to potentially do a bunch of unnecessary rebuilds... oh well ¯\_(ツ)_/¯

Bảng giá bạt xanh lá (xanh rêu), cập nhật 2026

Bạt xanh lá (hay còn gọi là bạt xanh rêu, bạt xanh lục) là dòng bạt che nắng mưa thế hệ mới đang rất được ưa chuộng hiện nay. Khác biệt với tông màu sắc sỡ của dòng bạt xanh cam truyền thống, bạt xanh lá sở hữu tông màu rêu trầm ấm, nhã nhặn, mang lại vẻ đẹp thẩm mỹ cao và sự mát mẻ cho mọi không gian sử dụng.

Để giúp quý khách hàng, nhà thầu và bà con dễ dàng lên dự toán ngân sách,Hàn Việt xin chia sẻ thông tin kỹ thuật chi tiết và công khai bảng báo giá sỉ lẻ bạt xanh lá trực tiếp xuất xưởng, hoàn toàn không qua trung gian thương mại.

Xem thêm tại: http s : / / bat nh uaha nviet . com. vn/

is it working?

God Bless memory-mapped I/O. The only part I like about kernel dev.

Converting everything in suphle v2 to attributes makes me wonder how much of framework constructs are just gathering metadata. But resulting userland code looks dreadfully arcane to me. Like an ugly new language or c#. Just because you can probably doesn't mean you should

One of the worst dev constructs I've ever seen are `final` classes. Both devs who added it to the language and library authors implementing it aren't gonna die well. Why even bother with oop if your shit classes shouldn't be extended for programmatic use? Psalm is the worst. Today, it was Symfony. Just realised I have to hard-couple to their clown mailer interface instead of my adapter cos I can't mock it. Why do you think your code is so flawless that nobody can ever improve or tweak it? Or use it outside the precise way you envisaged? Such hubris

If only everyone would shut the fuck up about AI.

We had a good opportunity, to quietly do more work with less effort, and enjoy the spare time.

But nooooo, virtue signaling pricks keep yapping about it with increasingly moronic expectations and now half the world is overworked, while the other half is jobless.

Big tech reaping record profits while the common folk struggle harder.

All because people can't shut the fuck up.
That's why we can't have nice things.

i shitted at least 8 times today