Comments on: API Design http://www.procata.com/blog/archives/2004/05/05/api-design/ PHP Programming, Web Development, PHP Advocacy and PHP Best Practices. Thu, 02 Sep 2010 05:14:22 -0400 http://wordpress.org/?v=2.8.6 hourly 1 By: Katie http://www.procata.com/blog/archives/2004/05/05/api-design/#comment-39133 Katie Mon, 06 Nov 2006 07:51:00 +0000 http://www.procata.com/blog/archives/2004/05/05/api-design/#comment-39133 Looking+for+information+ Looking+for+information+

]]> By: Mel Pullen http://www.procata.com/blog/archives/2004/05/05/api-design/#comment-238 Mel Pullen Mon, 11 Oct 2004 07:39:32 +0000 http://www.procata.com/blog/archives/2004/05/05/api-design/#comment-238 design by documentation is not new. The Sperry Univac 1100 mainframe operating system was not written until the reference manual had been written and approved. It's still a great idea. Anyone want to collaborate on a book? design by documentation is not new. The Sperry Univac 1100 mainframe operating system was not written until the reference manual had been written and approved.
It’s still a great idea. Anyone want to collaborate on a book?

]]> By: Jeff Moore’s Blog » Exceptional PHP http://www.procata.com/blog/archives/2004/05/05/api-design/#comment-28 Jeff Moore’s Blog » Exceptional PHP Tue, 25 May 2004 04:38:09 +0000 http://www.procata.com/blog/archives/2004/05/05/api-design/#comment-28 [...] was 15% less code (he was comparing compiled code size) and maybe 5% faster. Following my <a href="http://www.procata.com/blog/archives/2004/05/05/api-design/" title="API Design principles">API Design principles</a>, I think the smallest amount of c [...] [...] was 15% less code (he was comparing compiled code size) and maybe 5% faster. Following my API Design principles, I think the smallest amount of c [...]

]]> By: Jeff Moore http://www.procata.com/blog/archives/2004/05/05/api-design/#comment-21 Jeff Moore Thu, 13 May 2004 01:51:54 +0000 http://www.procata.com/blog/archives/2004/05/05/api-design/#comment-21 Maybe thats why I like SimpleTest so much. Designing the application by writing user documentation is not a new idea. I think that taking a tutorial oriented approach is a great idea because it focuses on the tasks that a user would want to do. User documentation that simply enumerated screens and menu items or that simply enumerated classes would not be good candidates for driving development. They are too much like the big design up front that the agile methodologies are trying to avoid. Writing tutorials doesn't sound much different than writing stories. (use cases, essential use cases, scenarios or whatever you want to call them, I have a fondness for task based UI design.) Maybe thats why I like SimpleTest so much. Designing the application by writing user documentation is not a new idea. I think that taking a tutorial oriented approach is a great idea because it focuses on the tasks that a user would want to do. User documentation that simply enumerated screens and menu items or that simply enumerated classes would not be good candidates for driving development. They are too much like the big design up front that the agile methodologies are trying to avoid. Writing tutorials doesn’t sound much different than writing stories. (use cases, essential use cases, scenarios or whatever you want to call them, I have a fondness for task based UI design.)

]]> By: Harry Fuecks http://www.procata.com/blog/archives/2004/05/05/api-design/#comment-20 Harry Fuecks Mon, 10 May 2004 23:11:53 +0000 http://www.procata.com/blog/archives/2004/05/05/api-design/#comment-20 Tutorial Driven Design - you may be onto something. Seriously. Course it's going to be hard for managers to swallow: "All coding begins... with a tutorial" Tutorial Driven Design – you may be onto something. Seriously. Course it’s going to be hard for managers to swallow: “All coding begins… with a tutorial”

]]> By: Marcus Baker http://www.procata.com/blog/archives/2004/05/05/api-design/#comment-19 Marcus Baker Mon, 10 May 2004 13:22:23 +0000 http://www.procata.com/blog/archives/2004/05/05/api-design/#comment-19 Hi. As an experiment the early versions of the <a href="http://simpletest.sourceforge.net/">SimpleTest API</a> used TDD - Tutorial Driven Design. I wanted to write a mock object article and so wanted to add mocks to PHPUnit. I was working out the interface through the article. The problems I encountered caused me to write my own test case class and shelve the article for nearly a year. Recently the API has been driven more by user requests, theft from the Java world (JWebUnit) and domain concepts (the web browser), but I am thinking that more than anything I should write another tutorial. yours, Marcus Hi.

As an experiment the early versions of the SimpleTest API used TDD – Tutorial Driven Design. I wanted to write a mock object article and so wanted to add mocks to PHPUnit. I was working out the interface through the article. The problems I encountered caused me to write my own test case class and shelve the article for nearly a year.

Recently the API has been driven more by user requests, theft from the Java world (JWebUnit) and domain concepts (the web browser), but I am thinking that more than anything I should write another tutorial.

yours, Marcus

]]>