Judging third-party libraries
This is a take-home review. You didn't use a single third-party library in the app you submitted, and the interviewer asks why not, and if you had to, which parts you'd swap for which library. Answer with your criteria.
This is a take-home review. You didn't use a single third-party library in the app you submitted, and the interviewer asks why not, and if you had to, which parts you'd swap for which library. Answer with your criteria.
The criteria are: is the standard framework enough, does the library solve a problem you actually have, and can you afford the maintenance, security, binary size, and lock-in cost. Networking and JSON are covered by URLSession and Codable; areas that are expensive to build yourself, like image caching and snapshot testing, are where you use one.
ArchitectureMultiple choiceBasics
Which of these correctly pair a situation with a design pattern? Select all that apply.
#adapter
ArchitectureShort answerAdvanced
You want to split an app that grew into a single target into modules. What criteria do…
#spm
ArchitectureMultiple choiceAdvanced
The SearchFeature module needs to open CheckoutFeature's payment screen from a search…
#dependency
ArchitectureShort answerAdvanced
You said you chose MVVM for this feature. When does MVVM actually hurt?
#trade-off