iosopt.hashnode.devQuestions and ReusabilityThe reusability is a very good concept. If a function or a module can be reused it is good because the code will be more clear, smaller, more modular, you won’t repeat your self, the solution will be nice. Let start building questions. This is our ba...Dec 23, 2025·3 min read
iosopt.hashnode.devBlueprint for Learning any ArchitectureWhile learning software architecture designs, I realized that many explanations are long and abstract. They often describe principles and blueprints, but rarely provide a single way to build an initial understanding. I often left that I need more tim...Oct 28, 2025·2 min read
iosopt.hashnode.devDisadvantages of reactive programmingThe reactive programming is good and useful. We know a lot of advantages of it. I would like to show some disadvantages. I hope with this will help you to use this technich in the right way Controll When you use an observ pattern like the Combine In ...Sep 20, 2025·5 min read
iosopt.hashnode.devStatless? Decoupled? Think Again. The Real cost of Combine in Complex systemAfter exploring Swift’s recommendation to “use struct by default,”I started thinking about how this impacts data ownership, freshness, and system design — especially in reactive contexts like Combine. In my previous post (link), I showed that structs...Apr 22, 2025·3 min read
iosopt.hashnode.devStruct vs Class in Swift: Understanding the Real Tradeoffs Behind the RecommendationSwift recommends struct by default – but why? Let's explore the hidden logic behind value semantics, Copy-on-Write (COW), and real-world performance tradeoffs. Value semantics with reference efficiency – under the hood Swift has an interesting recomm...Apr 20, 2025·2 min read
