It's getting harder and harder to write articles

[honey the codewitch]

As I dive into IoT arcana I'm still coming up with plenty of material which you'd think would be excellent fodder for articles, but it seems like these days all I'm digging up is so very specific to what I'm performing that it's hard to create a general article around. Like, the subject is good, but hard to generalize because it may only cover it from a very specific scenario. To make something that's general would be writing War and Peace here at CP and nobody has time for that. I'd really like to write an article right now about using I2S to stream audio to an internal or external DAC on an ESP32. You'd think "hey, that would be great, right?" The trouble is, my code is written for the M5 Stack Core2 and the Fire products and somewhat difficult to generalize (so far). :sigh: By the time I do generalize it, it will become part of a much more complicated library (SFX) and it will be hard to write articles for without losing the reader in a labyrinth of code. Instead I'll be forced to write articles on *using* SFX rather than how I coded it, which is a different topic. There's not really an in-between due to the nature of real time audio requiring a somewhat involved bit of infrastructure to support things like DMA transfers. I can code a pretty simple specific case, but generalizing it makes the complexity explode. I'm not really sure how to approach this, and feeling kind of frustrated right now.

To err is human. Fortune favors the monsters.