Search for a command to run...
I am an iOS Developer from Egypt, Cairo who likes Apple Products and UX studies
I enjoy reading about Entreprenuership and Scrum.
When no one is looking, I like to play around with Figma and build tools/ideas to help me during get things done quickly.
And I keep repeating epic gaming moments over and over again in my head and repeat narratives out loud in my room to regain a glimpse of how it felt when I first saw it (without altering the script)
No comments yet. Be the first to comment.
A series about a set of techniques that improves your project's fail tolerance and allows for better quality monitoring and UX
Have you ever been in a situation where your manager approaches you and mentions that there is a critical bug on production, and upon hearing the details, you’ve no idea what’s going on “out there”? You open up Xcode, try to reproduce the issue, and ...
Navigating the Complexities of Domain-Driven Design: Bridging Tech and Business with Clarity and Bounded Contexts
And the start of a Journey with another DDD Book
How Command Pattern can be easily translated to Siri features
Breaking the Chains of Massive View Controllers: Lessons for SwiftUI and Beyond
A New day... a new productive day where my tiny blog gains a new post! https://tenor.com/view/terrific-tuesday-gif-25021333 Today is a bit of a quick one, its about a productivity tip you can imply if you work a lot with terminals, so without furth...
Hello there! 👋
It’s been a while, and I really missed writing a blog early in the morning! Now that I have some sort of free time, I wanted to discuss some techniques in Error handling over the coming days that I learned, and well, thought it would be interesting to share! 😄
I wanted to start with something that may not be obvious all the time, especially when you prefer to be safe away from crashes, which is unwrapping optional variables
func handle(deeplink: String) {
guard let deeplinkUrl = URL(string: deeplink) else { return }
...
}
In the current context of the above method, you need to make sure that the URL is unwrapped after receiving the deeplink, and if the deeplink is invalid for whatever reason, we won’t continue executing the method
Seems… kinda normal, right?
Nope, it’s not always okay to early return silently, while it may not affect the program’s execution or create any bug (not always)… It may be a sign of something went wrong, without firing any alarms, like a bug hiding in plain sight, like a...
Silent Bullets are parts of your code that fail without firing any warnings, and the pattern where you unwrap a variable without handling the case where its indeed nil may create weird behaviors, and we, the developers, should be notified when something like this goes wrong
Logging such behavior should be what you do in such case, to give you a second pair of eyes when something goes wrong, be it a technical issue, bad usage from another team, or a glitch in the matrix
For the scope of this post, we will stop at just printing this issue, in the next post we will talk more about Logs and why you need them, then walk you through a better approach than just printing it
func handle(deeplink: String) {
guard let deeplinkUrl = URL(string: deeplink) else {
debugPrint("coudln't unwrap \(deeplink) as a URL for handling it.")
return
}
...
}
Not always unwrapping optional parameters may be a good thing, when reviewing/writing unwrapping code, ask yourself, is it normal for my use case that this variable may become nil by design? Or if it became nil that indicates a problem? 🤔
Happy Coding!
