Today I wrote about Kotlin/Android libraries I've been trying or saving for later.
When you're writing code every day, how do you figure out which bits are unusual or interesting enough to write about them? I find this tricky.
I still haven't found a navigation pattern I'm happy with on iOS. Everything I try that doesn't let view controllers know about and navigate to each other (which I hate), feels really awkward. But I'm sure there must be a better way.
It seems rare that docs alone are enough for me to implement a new feature, but these docs on the
UISearchController are detailed and quite clear.
I'm off to a gymnastics class today, and I'm really looking forward to getting away from all this internet drama and just focusing on tumbling, swinging, and lifting until I'm sore.
This might be a dumb question, but when Swift says I have to use
self. to call a function inside a closure, should I be using
weak self or something there, to avoid retain cycles?
It's pretty telling in terms of how well you listen to your community when those who aren't happy only feel comfortable saying so secretly, or outside the confines of the community itself.
I love using promises, but I wish I understand them better. I spend a lot of time fighting with the Swift compiler, using trial-and-error to get it to leave me alone, because I don't understand what the real problem is.
As soon as I left the hairdresser after my last haircut, I started growing it out. I really hated it. I can't wait to get it past the most awkward growing stage so I can have it cut into a new style.