Even better - redirect stdout to a file within the program!
kensand
Bing "on a saint"
I'm lazy, so I literally just use a Mason jar and a steel filter. Something like this.
It's probably not the most efficient, but it gets me my caffeine in the morning and tastes good to me!
That's the thing, nobody really knows!
And it's exponentially based on how many pixels those characters take up
And even with 'AuthN' vs 'AuthZ' it always takes me a minute to spell them out and work out which is which
What a coincidence, I just finished writing the first revision of my own bot for this. It's rough, but it works for me so far :)
I would generally say to stick to approach 1, as much as that stinks. Your observation about approach 2 especially compounds once you start to look at more complex operations that need to be optimized based on how the underlying DB works. Care still needs to be taken in approach 1 to avoid non-optimal operations, but at least you have the freedom to rework individual methods on your DatabaseProxy instead of all FirebaseProxy methods using your underlying CRUD operations.
One of the fastest ways I get people thinking about this is asking
How would you implement a
listTimers
orlistTickets
API with cursors?
Generally that's complex enough to bring out pain points.
Reads like an Onion headline
I'll never federate my instance at least
Love the birds flying by in the foreground.