Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • Excellent answer. Offtopic: Your example question #3 makes me curious. I am interested in knowing more on your opinions about layered design. Commented Apr 17, 2011 at 13:46
  • 2
    @missingfaktor #3, as stated, is a trick question to spark a conversation about things done quickly versus things done right. #4 and #5 are the same. #7 is probably the hardest, and only apt for leadership roles. Commented Apr 17, 2011 at 14:20
  • 1
    @missingfaktor I, again, gave an answer to a different question. This Wikipedia article, the related ones, and the external links provide a wealth of information about why separation of concerns is paramount to the design and construction of complex system: en.wikipedia.org/wiki/Modularity Commented Apr 17, 2011 at 14:30
  • Makes sense. Thanks a lot! :-) Again, excellent answer. Makes many good points not mentioned in other answers here. Commented Apr 17, 2011 at 14:41
  • Personally I would also add a question about tooling. People who care about the tools they use, tend to be be better programmers. As an Emacs user, I much prefer a vim user to someone who just shrugs their shoulders and doesn't care. Commented Jan 28, 2014 at 23:10