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.

7
  • 2
    Frame your thoughts as suggestions and ideas. Get THEM to talk through THEIR ideas before asking questions to make them think about yours +1 for that nonetheless Commented Apr 6, 2016 at 8:44
  • 2
    @rath Keep in mind that other people might not be reading from your book. It's possible that the person you're having the discussion with regards it as a confrontation, which could be counter-productive to your aims. Commented Apr 6, 2016 at 9:57
  • 2
    @rath: There is no right or wrong. Just trade offs. And more often than not the trade offs involve more than code alone. Commented Apr 6, 2016 at 11:23
  • 1
    @Dunk All that exist are trade-offs. We call them right or wrong when the trade-offs are crystal clear and obviously on one side. However recognizing when that shades into ambiguous is easier if we focused on them being trade-offs from the start. Commented Apr 6, 2016 at 19:24
  • 2
    There is not a single programming "best practice" that I'm aware of which doesn't have exceptions where it is not best. Sometimes it is hard to find those exceptions, but they always exist. Commented Apr 6, 2016 at 19:26