Code Against Interfaces, Not Implementations - Revision history

JaroslavTulach: /* Have You Ever Wondered...? */

2025-02-15T04:15:23Z

Have You Ever Wondered...?

←Older revision		Revision as of 04:15, 15 February 2025
Line 2:		Line 2:

	Have you ever participated in a flamewar between people who believe API should be full of '''interface'''s and those who believe it is better to use '''class'''es? Was the dispute resolved somehow or people just kept their original views? Yes, I've participated in such discussions few times and yes, they never lead to any conclusions. However then I've managed to look at the old ''code against interfaces'' advice in new light and things started to make sense. Since then I have eliminated flamewars of this kind almost completely. Probably because the revelation is not only surprising, but also backed by rational reasoning. You can find this all in the chapter 6, plus see application of this rule for [[APIDesignPatterns:RequestResponse\|Request/Response]] API Design Pattern.		Have you ever participated in a flamewar between people who believe API should be full of '''interface'''s and those who believe it is better to use '''class'''es? Was the dispute resolved somehow or people just kept their original views? Yes, I've participated in such discussions few times and yes, they never lead to any conclusions. However then I've managed to look at the old ''code against interfaces'' advice in new light and things started to make sense. Since then I have eliminated flamewars of this kind almost completely. Probably because the revelation is not only surprising, but also backed by rational reasoning. You can find this all in the chapter 6, plus see application of this rule for [[APIDesignPatterns:RequestResponse\|Request/Response]] API Design Pattern.
		+
		+	Lower [[Conceptual surface]] of your API by hiding the gory implementation details.

	== [[Errata 6\|Errata]] ==		== [[Errata 6\|Errata]] ==

	{{:Errata 6}}		{{:Errata 6}}

JaroslavTulach: /* Have You Ever Wondered...? */

2010-10-08T07:27:29Z

Have You Ever Wondered...?

←Older revision		Revision as of 07:27, 8 October 2010
Line 2:		Line 2:

	Have you ever participated in a flamewar between people who believe API should be full of '''interface'''s and those who believe it is better to use '''class'''es? Was the dispute resolved somehow or people just kept their original views? Yes, I've participated in such discussions few times and yes, they never lead to any conclusions. However then I've managed to look at the old ''code against interfaces'' advice in new light and things started to make sense. Since then I have eliminated flamewars of this kind almost completely. Probably because the revelation is not only surprising, but also backed by rational reasoning. You can find this all in the chapter 6, plus see application of this rule for [[APIDesignPatterns:RequestResponse\|Request/Response]] API Design Pattern.		Have you ever participated in a flamewar between people who believe API should be full of '''interface'''s and those who believe it is better to use '''class'''es? Was the dispute resolved somehow or people just kept their original views? Yes, I've participated in such discussions few times and yes, they never lead to any conclusions. However then I've managed to look at the old ''code against interfaces'' advice in new light and things started to make sense. Since then I have eliminated flamewars of this kind almost completely. Probably because the revelation is not only surprising, but also backed by rational reasoning. You can find this all in the chapter 6, plus see application of this rule for [[APIDesignPatterns:RequestResponse\|Request/Response]] API Design Pattern.
		+
		+	== [[Errata 6\|Errata]] ==
		+
		+	{{:Errata 6}}

JaroslavTulach: /* Have You Ever Wondered...? */

2008-08-02T20:27:53Z

Have You Ever Wondered...?

←Older revision		Revision as of 20:27, 2 August 2008
Line 1:		Line 1:
	== Have You Ever Wondered...? ==		== Have You Ever Wondered...? ==

-	Have you ever participated in a flamewar between people who believe API should be full of '''interface'''s and those who believe it is better to use '''class'''es? Was the dispute resolved somehow or people just ~~keep~~ their original views? Yes, I've participated in such discussions few times and yes, they never lead to any conclusions. However then I've managed to look at the old ''code against interfaces'' advice in new light and things started to make sense. Since then I have eliminated flamewars of this kind almost completely. Probably because the revelation is not only surprising, but also backed by rational reasoning. You can find this all in the chapter 6, plus see application of this rule for [[APIDesignPatterns:RequestResponse\|Request/Response]] API Design Pattern.	+	Have you ever participated in a flamewar between people who believe API should be full of '''interface'''s and those who believe it is better to use '''class'''es? Was the dispute resolved somehow or people just kept their original views? Yes, I've participated in such discussions few times and yes, they never lead to any conclusions. However then I've managed to look at the old ''code against interfaces'' advice in new light and things started to make sense. Since then I have eliminated flamewars of this kind almost completely. Probably because the revelation is not only surprising, but also backed by rational reasoning. You can find this all in the chapter 6, plus see application of this rule for [[APIDesignPatterns:RequestResponse\|Request/Response]] API Design Pattern.

JaroslavTulach at 20:27, 2 August 2008

2008-08-02T20:27:25Z

←Older revision		Revision as of 20:27, 2 August 2008
Line 1:		Line 1:
-	~~Old~~ and ~~good~~ advice in new light. ~~Plus its~~ application for [[APIDesignPatterns:RequestResponse\|Request/Response]] API Design Pattern.	+	== Have You Ever Wondered...? ==
		+
		+	Have you ever participated in a flamewar between people who believe API should be full of '''interface'''s and those who believe it is better to use '''class'''es? Was the dispute resolved somehow or people just keep their original views? Yes, I've participated in such discussions few times and yes, they never lead to any conclusions. However then I've managed to look at the old ''code against interfaces'' advice in new light and things started to make sense. Since then I have eliminated flamewars of this kind almost completely. Probably because the revelation is not only surprising, but also backed by rational reasoning. You can find this all in the chapter 6, plus see application of this rule for [[APIDesignPatterns:RequestResponse\|Request/Response]] API Design Pattern.

Apidesign at 05:53, 14 June 2008

2008-06-14T05:53:02Z

←Older revision		Revision as of 05:53, 14 June 2008
Line 1:		Line 1:
-	Old and good advice in new light.	+	Old and good advice in new light. Plus its application for [[APIDesignPatterns:RequestResponse\|Request/Response]] API Design Pattern.

Apidesign: New page: Old and good advice in new light.

2008-06-14T05:49:23Z

New page: Old and good advice in new light.

New page

Old and good advice in new light.