bgeek.net

CodeCamp: in need input

Posted by Owen Evans on Monday, August 18th, 2008

Ok so this is a bit of a plea.
I’ve a week or so to work on my CodeCamp presentation “MVC and Me” (ok so would have been cooler to link to flight of the navigator but that’s too hard for me to pull off) and I’m still trying to gather as many ideas about what [...]

continue reading

Split And Sprint

Posted by Owen Evans on Thursday, August 14th, 2008

In a forthcoming book (before you ask I’ve no idea what the title is) there’s a little case study about the first project i ever truly worked on as a developer. The project and the team have some of my fondest memories, and I’d want to work with any of the people in the small [...]

continue reading

Post 300

Posted by Owen Evans on Friday, August 8th, 2008

Ok I just had to cheat an make up a reason to post. But this is my 300th post, this blog has been going for more than 5 years (25 Feb 2003 was my first post, those heady days of university). that’s 1992 days, so an average of one post every 6.64 days. (my goodness [...]

continue reading

Is that you?

Posted by Owen Evans on Friday, July 18th, 2008

I didn’t recognise you it’s been so long.

I finally got the urge and the patience to fire up my editor and write a post for this long neglected weblog.

How are you all doing? good I hope?

Ok so I may have been prompted to write by a link from Julian over at ProWorkflow but I’m here now and that’s all that matters, isn’t it?

But what to write about? That’s one reason I’ve not posted an update for so long, I’ve been keeping my head down getting as much done at Xero as possible, and not really coming up for air.

So a couple of posts that I’ve been meaning to write and never got around to:0

  • Email and the myth of standards (or how I created a chain of 3000 emails in an hour),
  • How to keep your eye on the goal and not be distracted by the shiny fruit of extra features
  • Why estimation is sooo hard
  • Why estimates are so useful

For now I’m going to be terse and keep things concise.

Open Question: What makes a good API?

So you’ve got a product that loads of people could potentially tap into the use of if only there was a clear and concise way of tying in their existing product line into yours. So you need an API, but an API is useless unless people actually use it.

 

economizing,Electrical Component,Power Line,Electricity,Concepts,Technology,Alternative Energy,Efficiency,Single Object,Cable,Clip Art,Web Button,Smooth,Colour,Illustration and Painting,Design Element,Symbol,Sign,Web 2 0,Two Pin Plug,Label,Isolated On White,Simplicity,Environmental Conservation,Green,Gradient,Shadow,White,Energy,Electrical PlugAt the moment Xero has a functional and useful API that’s available to our many Network partners , we love the idea that people can do many of the great features that we can’t get round to right now (and I’m not sure we’d want to). Easy accounting is our goal and allowing you to use the solution for Payroll or Project management that suits you and get as much generated in Xero as possible really suits us down to the ground.

But an API is only as good as the tools that use it, and we rely on development effort to get the external products working well with Xero, we’ve tried to make the API as clean as possible, but we really need feedback.

What do you want from an API? What makes an API easy to use for you?

Interested in feedback.

This is not a Xero mandated survey, I’m just interested in what people think about API’s and what makes them good.

Sphere: Related Content

Posted in: [||].

discussion by DISQUS

Add New Comment

blog comments powered by Disqus