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. 😉
It takes 12 (kind of)simple things such as taking responsibility for your own happiness, living for the struggle, manage your emotions, showing patience and restraint, being indepdendent and vulnerable and expecting the same from others. You know, easy stuff like that. 😉
I mean, you have to give her points for trying. 🤷🏻♂️ She put her entire weight into pumping up my bike tire, with limited results. #goodtrythough #bikelife #bike #fairdalebikes #kid #austin #texas #atx #shotoniphone via Instagram https://instagr.am/p/CFFblBXlQKz/