In many ways, DITA and docs-as-code are polar opposites - one a highly structured, semantic methodology, the other a more flexible, developer-driven approach. When faced with the question of choosing the right approach for their use case, technical writing teams sometimes struggle to meaningfully compare the two. In this presentation, I'll share my experiences from working with two similar yet different organizations: Company A, which uses DITA, and Company B, which uses docs-as-code. We'll look at the costs and benefits of each approach, and how their respective implementations can shape your documentation process.