Why is the Single Responsibility Principle important?
What is Inversion of Control? How does that relate to dependency injection?
How does a 3 tier application differ from a 2 tier one?
Show me a portfolio of all the applications you worked on, and tell me how you contributed to design them.
What are some alternate ways to store data other than a relational database? Why would you do that, and what are the trade-offs?

Question

Why is the Single Responsibility Principle important?
What is Inversion of Control? How does that relate to dependency injection?
How does a 3 tier application differ from a 2 tier one?
Show me a portfolio of all the applications you worked on, and tell me how you contributed to design them.
What are some alternate ways to store data other than a relational database? Why would you do that, and what are the trade-offs?

Will S. · Accepted Answer

Single-responsibility principle forces us to abstract reusable concepts in our code.  In turn, this will help make our code far less brittle when requirements change.

Anonymous · Answer

It amazes me how so many developers out there think that OO is nothing more than "classes with methods/members on them" and maybe "inheritance for sharing functionality." Also, I've found myself in some really interesting conversations with good developers on this subject. It segues pretty well into other topics too, such as some SOLID principles and interfaces.

Whole Foods Market

Whole Foods Market interview question

Interview Answers

Want the inside scoop on your own company?

Bowls

Followed companies

Job searches