interviews for less-established (or famous) devs are rarely about what you will do on the job. It's like they just want to verify that you went to a formal university NOT that you can build an app properly and structure it for maintainability. I can see SOME value in that; but how many good app developers have been turned away because they couldn't whip up an algorithm for a problem space that they'll never be asked to do at the office? If my job isn't going to be making obscure algos, then don't test me on that.
Hi Christopher, not every company will ask data structure/algorithm questions. It's a matter of finding a company that will be a good fit for what you're looking for ✅
@Essential Developer Just an extension to the router discussion ...so suppose if there are multiple screens on which to navigate from a particular view controller so how would you suggest to structure that ---- using enums representing screens names or any other way in order avoid enum switching for navigation logic
Hi! We don't recommend enums as a go-to solution to this problem because they are usually too rigid (e.g., adding a new case is a breaking change). So we'd use enums only when really needed. In most cases, I would recommend a solution using polymorphism instead. So new screens can be added without breaking existing code ✅
interviews for less-established (or famous) devs are rarely about what you will do on the job. It's like they just want to verify that you went to a formal university NOT that you can build an app properly and structure it for maintainability. I can see SOME value in that; but how many good app developers have been turned away because they couldn't whip up an algorithm for a problem space that they'll never be asked to do at the office? If my job isn't going to be making obscure algos, then don't test me on that.
Hi Christopher, not every company will ask data structure/algorithm questions. It's a matter of finding a company that will be a good fit for what you're looking for ✅
@Essential Developer
Just an extension to the router discussion ...so suppose if there are multiple screens on which to navigate from a particular view controller so how would you suggest to structure that ---- using enums representing screens names or any other way in order avoid enum switching for navigation logic
Hi! We don't recommend enums as a go-to solution to this problem because they are usually too rigid (e.g., adding a new case is a breaking change). So we'd use enums only when really needed. In most cases, I would recommend a solution using polymorphism instead. So new screens can be added without breaking existing code ✅
@@EssentialDeveloper Hi , is there any example with this approach?
Hi! Yes, in the iOS Lead Essentials program (but it's only available to students).