Love what you create

Article by: Peter Thiess

Love what you create

I love what you create

My name is Peter Thiess and I’m the engineering manager of the Brackets core team and a few related initiatives here at Adobe. After more than a decade developing proprietary software, it’s my pleasure to work on a project like Brackets and really exciting that Adobe has invested in this open source project.
Ever since I worked with tools like KDevelop and Subversion, or libraries like curl, the passion and dedication of Open Source contributors like Daniel Stenberg, have encouraged me to believe that there is a humble and humane force behind coding. Open Source is social coding and has always been, but it never felt as close as with Github; respect — you guys changed the world, yeah!

Individuals like Marijn Haverbeke or Tomás Malbrán have gained my deepest respect while working on Brackets. In addition, every single contributor to Brackets thrills and motivates me and my team every day. Not that one needs a lot of additional motivation to work on Brackets. It’s a real honor and a lot of fun to work with such smart engineers and an astonishing community. I love what you create!

Brackets was started roughly two and a half years ago and the enthusiasm of the community as well as user acquisition has been mind blowing. We not only build an Open Source project but we also depend on a number of other incredible projects. Projects like CodeMirror and the Chromium Embedded Framework are the foundation upon which we, the Brackets community, built this product. While the team here at Adobe is core to this endeavor, as good citizens of this community we only intend to control as little as possible. We wish to provide enough insights into how we as Brackets committers operate to enable great new things like the coding surface in Intel’s XDK.

Development and prioritization
For the most part, we used traditional SCRUM as our development process. We were a little bit creative, defining research stories to learn how to do things right before we went ahead and broke them down further. Then we discovered that swarming is a powerful technic and lets us do things seamlessly in parallel. Soon we built or own Brackets development process to fit our needs.

And still time boxing and some of the more prescriptive elements of the SCRUM process limited our abilities to progress in a lean and agile fashion. Kevin Dangoor outlined that in one of his personal blog posts “The Brackets SCRUM to Kanban switch“.
This is an ongoing improvement, but the general idea to break down large features into medium and small work items works well – the Split View epic may be a great example to look at. The Trello card lists the work items and each work item lists their dependencies. You may follow the flow in our public board. If you are eager to learn more about our approach to Kanban please find the “Brackets developer’s guide” in our wiki.

We’d be happy to hear your feedback.

Peter Thiess

Leave a Reply

Your email address will not be published. Required fields are marked *