Blog posts by Sarah Allen (18F alumni):

In the final part of our series on technical debt, we talk about ways to minimize accumulating bad or unnecessary technical debt in the first place.

In the last post in this series, we talked about the potential consequences of having a lot of technical debt. Now, we’ll give you concrete steps to identify and then manage that technical debt so it doesn’t get out of hand.

In part two of our series on technical debt, we define what technical debt is and how it can negatively impact your organization or project.

Technical debt is a financial metaphor that software developers use to talk to managers about the “hidden” costs associated with a system’s architecture and codebase. Over a series of upcoming posts, we’re going to explain what technical debt is, how to manage it, and some ways to prevent accumulating it.

It has become a standard practice in the software industry to create a “code of conduct” for conferences and events. By creating our own Code of Conduct, we are defining the kind of environment we seek to create.

The October Oopen source hack night was a huge success, both as a community event and for the positive impact on the Midas project.

18F invites designers and developers from inside and outside of government to join us for a flurry of coding and sketching. Midas is an open source project in active development by 18F, Health & Human Services (HHS) IDEA Lab and the State Department. A small cross-agency team, dedicated to launching this product to empower passionate civil servants and aspiring diplomats all over the world.