Archives for the tag: developer

I've been writing a lot of documentation lately. On the Stash team we keep the bulk of our developer documentation in the Stash git repository, right alongside our production code. This approach means that as we introduce new plugin points, developers can review and critique the documentation for those plugin points in the same pull request as the code change. This has proved a convenient feedback mechanism and has made keeping our developer documentation up-to-date much easier. We use markdown syntax

Continue reading »

The Tool is the Easy Part - What about the Processes? The FishEye team was the first team at Atlassian to make the switch to DVCS, and while some Atlassians had previous DVCS experience, quite a few had not yet used it in the workplace with a medium-size team of developers before. We looked for help around the web, but there wasn't a lot of people sharing their experiences at the time. We found many resources like "How do I push a branch in Git?" or "How do I pull from multiple remotes in Mercurial?",

Continue reading »

AtlasCamp EU Videos Now Online!

For those who missed the event, the AtlasCamp Europe 2012 videos are now online. This AtlasCamp was our first ever developer event in Europe and it was a smashing success. Thanks for all who made it possible. Here are the talks: Keynote -- Jean-Michel Lemieux, VP of Engineering, Atlassian All About the Marketplace -- Jonathan Nolen, Director of Developer Relations, Atlassian Licensed to Sell: How to use Atlassian's new Licensing API to Sell your Plugin on the Atlassian Marketplace -- Ben

Continue reading »

Stable APIs? Yes, we have them.

I think we can all agree that building a software product is difficult. What's even more difficult is maintaining it. It's particularly difficult and frustrating when the APIs you've come to depend on change from under you. Changing APIs between minor releases negatively affects the developers who rely on it for their products, the customers who bought that developer's product, and the users of that product. This is a problem with many software ecosystems today and that used to be the case for plugin

Continue reading »

The Atlassian technical writers and thirteen developers recently combined forces in a doc sprint. The aim? To develop plugin tutorials that will help people use the upcoming JIRA 5.0 Java APIs. The result is eleven shiny new tutorials and plenty of updates to existing pages. The indomitable doc sprinters were based in Sydney, San Francisco and Gdansk. We got together in chat rooms, in video conferences and on the wiki. What is a doc sprint? A doc sprint is an event in which people get together

Continue reading »

Building an Ecosystem for Hackers

A couple of weeks ago, I presented at QCon SF. My topic was on Building an Ecosystem for Hackers. It was a talk about how we empower our users (yes, users – who mostly happen to be developers) to hack on our products for fun and profit. The sentiment of the talk focused on the fact that having a platform that empowers its users and developers is a great thing. Hackers in the context of my talk are developers and users. Not all "hackers" have bad intentions. While working on this talk, it dawned

Continue reading »