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*

14
  • 8
    Badly designed anything isn't good. Building an API isn't more time and is more future-proof. The ability to adapt to change being vital nowadays, better build a strong base to fulfill any needs that you don't even know about but that might come sooner than you think... Commented Jun 25, 2015 at 21:37
  • 11
    @Bartdude: Introducing needless complexity for the sake of "future-proofing" for a future which will not arrive is just wasting resources. Commented Jun 26, 2015 at 6:52
  • 6
    @Bartdude adding an api is definitely more time. No idea how you think you can claim otherwise. Commented Jun 26, 2015 at 7:19
  • 15
    "you shouldn't introduce a web service layer" API != web service. If you have your business logic behind an API, then you can expose that API as a web service at some point. It's not an up-front requirement, though. Commented Jun 26, 2015 at 7:35
  • 2
    @JacquesB : ... so you indeed don't develop features if you're not sure you're going to need it. That's what I understand from YAGNI. Yet architecture is not a feature and bad architectural choices can (and most probably will) lead to a miserable failure. Once again I assume this discussion can even occur, which is sometimes not the case was it for budget, time-to-market, ressources or lack-of-knowledge reasons... I think we can totally agree to disagree on this, although I understand your point as I often had the same discussion with myself ^_^ Commented Jun 26, 2015 at 8:56