InBack Market BlogbyAlberto Salas·Jan 5Back Market x Tuist - Part III: How We Enforce Our Modularization Strategy with TuistTurning architectural rules into code with Project Description Helpers
InBack Market BlogbyAlberto Salas·Nov 10, 2025Back Market x Tuist II: How We Migrated Our iOS Project From SwiftPM to TuistFrom planning to execution: what we did, what worked, and what we learnedA response icon4A response icon4
InBack Market BlogbyAlberto Salas·Nov 3, 2025Back Market x Tuist - Part I: Why We Moved Our iOS Project To TuistWhat wasn’t working, what we explored, and why Tuist made sense for us.
Alberto Salas·Apr 21, 2020YAGNI: You Ain’t Gonna Need It - Part II: Hands OnDeveloping A Newspaper App
InBetter ProgrammingbyAlberto Salas·Mar 6, 2020YAGNI: You Ain’t Gonna Need ItDo not add functionality until it is completely necessaryA response icon3A response icon3
InBetter ProgrammingbyAlberto Salas·Oct 4, 2019Swift: Favor Composition Over Inheritance. The BaseViewController case.The BaseViewController caseA response icon1A response icon1
InBetter ProgrammingbyAlberto Salas·Aug 5, 2019Swift: Why You Should Avoid Using Default Implementations in ProtocolsDefault implementation, composition over inheritance, the interface-segregation principle, method dispatch, and unit testingA response icon7A response icon7
InBetter ProgrammingbyAlberto Salas·Aug 4, 2019Swift Optionals: Beyond BasicsMapping and flatMapping optionals for cleaner codeA response icon2A response icon2
InBetter ProgrammingbyAlberto Salas·Jul 27, 2019Swift: Beyond Switching on a ResultSwift.Result’s potential goes beyond just getting the value/error using a switch clause. Let’s look at a few things you can doA response icon2A response icon2