-
ATO processes work differently at different federal agencies. As a technology and design consultancy inside the United States government, 18F has worked on ATOs at many of them. We are still learning and experimenting, but there are definite patterns we have seen work well across multiple agencies.
Continue reading about Navigating ATOs -
If you have ever led or managed a web project, you know that coordinating a team of software engineers is hard work! We hope this blog post can help you understand the concepts behind choosing a web application architecture, so that you can steer your software towards simplicity — even if you don’t have direct software engineering experience.
Continue reading about Why simplicity? Choosing a web architecture -
No policy or rule stays the same forever. In response to a crisis, policy changes often come much faster, and stakes can be higher.
Continue reading about Rapid implementation of policy as code -
In software, a README is the documentation that tells you how to start using and understanding a new piece of software. In an organization, a personal README is a way to tell your coworkers how they can best communicate with you, work with you, give you feedback, and support you.
Continue reading about READMEs for you and me -
Don’t let your agency waste knowledge and opportunity. Instead of planning for a handoff to operations and maintenance, plan for a long-term team. Instead of launching your project and then keeping it running, plan for ongoing development.
Continue reading about Long-term teams, not sudden handoffs -
To be inclusive and effective, a team needs a culture where everyone is respected, treated fairly, and feels that they belong. We don’t see this diversity, equity, and inclusion work as a “nice-to-have” or optional.
Continue reading about Measuring culture on our engineering team