Archives for the tag: developer

Successful product teams incorporate user feedback throughout their development cycle. Product owners meet with customers.  Development teams respond to bug reports internally and issues from the field.  For user feedback to be helpful to the program, it needs to be actionable.  For the developers in the audience, how many of you have seen bug reports like this? As developers, that type of bug report doesn’t give us much to go on.  Ill formed issues are a central developer pain point.

Continue reading »

5 tips for great code reviews

In almost every organization, team members collaborate to get work done. Software teams typically transition issues between people for different functions like code development, code review, and testing (even if they are all on the same team). When transitioning an issue from one team member to another it’s important to minimize the amount of ramp up required for the receiver to fully understand the issue. Transferring issues can be extremely expensive as it requires time from not only one,

Continue reading »

This guest post comes courtesy of Carolyn Van Slyck, a full-stack software developer and a newly converted champion for Git. Carolyn has recently spearheaded her team's source code migration from SVN to Git with the help of Stash and subgit. She will be sharing her learnings and wisdom with us today. Redefining what is possible I work at a large software company which is heavily invested in Subversion. In my division alone, we have 3 repositories, each with 100+ projects. I don't even know how

Continue reading »

Building a better robot

What if we could respond to emergencies better? What if the obstacles that put human beings in danger – fire, structural collapse, radiation – were less of an issue, and more lives, property, and wildlife could be saved? This is the thinking behind the DARPA Robotics Challenge (DRC), which Atlassian Developer evangelist Tim Pettersen is competing in as part of the Institute for Humane and Machine Cognition (IHMC) team. The IHMC team is building software for Atlas, constructed by Boston

Continue reading »

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 »