Software Dev

Algorithms Interview Rant πŸ™Œ

It’s great to hear another dev just flat-out rant about the stupidity of “the algorithm interview”. Or as I call it, the “Computer Science 101” interview.

This podcast is basically saying that an effective interview should focus on things that you actually do on the job. In what crazy world are we interviewing for one skill and hiring for another?

I’ve been through a few “algorithm” interviews. They’re not that hard. They’re just annoying and misguided.

We are not in college any more. We are solving real-world problems.

The hardest technical interview I ever had as an iOS developer focused on things like the trade offs between different approaches to concurrency, effective testing at different levels, dependency management, and optimizing table views. These are much more interesting problems than a binary search.

If you do a computer science 101 interview, I guess you get to hire a bunch of computer science students. πŸ€·πŸ»β€β™‚οΈ

Software Dev

MVC: Many View Controllers

Another counterpoint in the iOS architecture wars, saying basically that MVC is actually pretty sound as long as you use it wisely.

This post breaks controllers down into a few types: Containers, Generic controllers, View controllers, Flow controllers to help reframe things.

One of my favorite points here is that not everything has to be a model, a view, or a controller. You can — and should — create other kinds of code! No wonder your controllers are messy if you limit yourself like that. πŸ€·πŸ»β€β™‚οΈ

This issue happens when the developer thinks they must fit everything into either M, V or C, forgetting that they are allowed to create other types of constructs.

πŸ‘‰ MVC: Many View Controllers

2

Via iOS Dev Weekly.