If there is one thing that I have learned in my career it's that network connectivity is not a binary state. A network connection goes through many different transitions when setting up the connection, transmitting data, and closing down the connection. In most cases, a client side mobile or desktop application can simply send the network request and if the client application is offline the request will immediately fail and the application can update the user accordingly (See article here). However, the
The landscape of mobile connectivity has become highly complex over the last 10 years. Our modern society has been built around the need to always be up and connected. And in most cases mobile connectivity works very seamlessly when driving, flying, transferring between cell towers, or even just going on a run - you stay connected. 10 year ago this type of connectivity was not that seamless, cellular voice transmission worked well, but cellular data transmission, and GPS coordination were often a challenge.
Throughout my career I have always been in a role that requires technical leadership in some capacity or another. Whether that means managing the day to day development of a product, creating technical solutions for a client, or just mentoring and guiding my team to make sure they are as successful as possible. Being a technical leader can end of being a lot of different things in a lot of different situations. However, no matter what type of technical world you exist in, or what type of development practice you use, there are a few things that I have learned that can always make you suc
TCPdump is one of my favorite network packet analysis tools in existence today. In the past year I have enjoyed TCPdump so much that I have wanted to learn more about the project. So, I thought a good place to start would be to get involved contributing on GitHub. My contributions are not much, but they help me learn the ins and outs of the project and how to use some of the more advanced features as I come up in issues or pull requests. During my time thus far I have noticed that a lot of filtering questions tend to come up on how to use filters or how to interpret the documentation fo
What’s new in Swift is a news feed that focuses on the latest articles, trends, and stories happening around the Swift ecosystem that I find interesting. All of the topics selected in this article have been cherry picked from either Github, Swift.org, or found the Swift Forums over the last few weeks and can range from topics covered in iOS, macOS, tvOS, watchOS, or in the Server Side community.
No matter your role or skill level on the project, performing code reviews as a team member or individual contributor to any project is very important. Performing code reviews is a valuable tool for all parties involved. It allows the reviewer to provide their thoughts or feedback on a topic and it allows the author the author to receive feedback on documentation or code that they have written. The question I find a lot of people asking, including myself, is how do I know that I am providing an effective code review for the author of this contribution?