I get interested in this kind of stuff in an attempt to avoid the "barely working" quagmire, which has it's own problems (namely, ongoing maintenance when it st

I get interested in this kind of stuff in an attempt to avoid the "barely working" quagmire, which has it's own problems (namely, ongoing maintenance when it stops working.) Less for reuse - what abstractions will help me avoid bugs? Which abstractions can simplify this and make it faster to write or modify? Which will be easiest to read and thus maintain? It's rare - although not impossible - that the answer to any of these things is "callback hell". "Reusable" just sounds too similar to "YAGNI violation" to me these days.