Plurrrr

Rust has a steep learning curve.

Once you're fully immersed in it, as with any skill, it becomes very difficult to properly remember what exactly made Rust difficult to learn. In a general sense, it could be the fact that it exposes the average programmer to some new features, most of them not present or only just beginning to show up in mainstream languages, and some that are close to unique.

For inserting SF Symbols in SwiftUI, I typically rely on Apple's SF Symbols app to browse the symbols's catalog. Once I find a symbol I'm happy with, I copy its name and paste it into my Swift source. This works fairly well.

With Christian Tietze recently posting how he rendered SF Symbols in Emacs, I figured there may be a way to shift the above workflow to rely on Emacs completion instead. While I initially went down a rabbit hole to programmatically extract SF symbols (via something like SFSafeSymbols), I took a step back to rethink the strategy.

A few weeks ago my colleague and I were talking about the pros of using a queue to take some work out of the request cycle. He read an article that suggested that queues should be used for all external calls. I disagreed. Making broad recommendations like that generally don't pan out because there are always tradeoffs. It's bound to be much nuanced than that. In this article I want to explore a few considerations worth exploring before you jump to using a queue.

Follows a dad who finds time for himself for the first time in years while his wife and kids are away. He reconnects with a friend for a wild weekend.

The bumbling Mr. Bean travels to America when he is given the responsibility of bringing a highly valuable painting to a Los Angeles museum.

A weekend getaway to Croatia that goes awry when a woman is accused of killing her best friend. As she attempts to clear her name and uncover the truth, her efforts unearth a painful secret.