You

Get Ready For The Roaring 2020’s

I’ve been saying for a few months that I really want to make the most of this awful pandemic. Stuck at home with time on your hands, it’s a great chance to focus and reinvent yourself. So I loved seeing this post touting the idea that we’re just getting ready for the next phase of our lives individually and collectively.

Prepare for the Golden Age: Why The Next Decade Will be Awesome

This post says that people will thrive in the coming years if they have the right attitude and beliefs, or dwindle if they let the changes in the world beat them down.

Many of us have spent the past year not just coping with the present moment, but getting better. When the conditions are back to normal, weโ€™re already going to have momentum. The golden age is upon us.

Is this just wishful thinking? Maybe so, but your beliefs tend to become your reality, so this is a good starting point.

And as more people believe this, the more real it will be for everyone.

The world has been through much worse than the current situation and come out better on the other end. Make the most of it.

I just feel something in the air. I feel an awakening. I have this strong conviction that a large portion of society is just done with the pessimistic outrage culture nonsense. Weโ€™re ready to take control of not just the discourse, but our own lives.

Happy roaring 2020’s.

Image for post
Software Dev

A Case For Force-Unwraping! Optionals in Swift

This topic came up at work last week, with lots of different opinions on how to deal with optionals, so I was happy to see a clear opinion here.

๐Ÿ‘‰ The Danger of Playing it Safe

For any non-programmers reading this, a force-unwrap means that if your app comes across a value that just simply doesn’t exist at all โ˜, then let the app crash right then and there ๐Ÿ’ฅ.

This article distinguishes between development, where it’s okay (and in sometimes encouraged) to crash, and production, where it’s never okay. I like the case here for avoiding poisoned app states that can occur with nil values. Just die already, already! ๐Ÿคท๐Ÿปโ€โ™‚๏ธ This article basically says that some development crashes are good because they expose problems, and to take a more aggressive approach with force unwrapping.

So be assertive with forced unwrapping. If there is no case where the optional should ever be nil, force unwrap

I think I’ll start taking more chances with force unwrapping and point to this article next time it comes up in a code review. ๐Ÿ˜‰

Via iOS Dev Weekly.