Just that given where we are in Swift 5.1 the idea that people are still force unwrapping optionals and not doing guards is a bit of a stretch.

They’re definitely bad code smells and would be called out in any code review I ran.

If they’re not, I’d strongly suggest that your team install SwiftLint into your project and make it part of the build process. Cleaning questionable code and enforcing coding standards is a must in modern Swift software development.

Michael Long is a Senior Lead iOS engineer at CRi Solutions, a leader in cutting edge iOS, Android, and mobile corporate and financial applications.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store