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
  • 89
    +1 for "we are typically very bad at predicting the future" The user will most likely ask for E :) Commented Sep 6, 2011 at 11:57
  • 1
    +1 Couldn't agree more. I recently finished a work term at a company, and I would consider this the most important lesson I learned. Commented Sep 6, 2011 at 13:22
  • 4
    @Michał, is that a prediction? ;-) Commented Sep 6, 2011 at 13:27
  • 10
    Even if they ask you for D, they will probably have a different mental model of it, and will ask for a slightly different kind of D which your abstractions don't support... Commented Sep 6, 2011 at 16:40
  • "If a problem is not completely understood, it is probably best to provide no solution at all" or "Do not add new functionality unless an implementor cannot complete a real application without it." applies here. Via en.wikipedia.org/wiki/X_Window_System#Principles Commented Apr 23, 2012 at 20:20