This will be a light-hearted session about the omnipresent war between software engineers and technical writers (documentation engineers) when working on projects.

Battle 1: Prioritization
Software engineers prioritize coding and do not give heed to doing things in a way that makes documentation easier.

Battle 2: Definition of Done
For software engineers, it is when a feature is done. For documentation engineers, it is when a feature is well-documented, thus leading to some conflicts.

Battle 3: Speed vs Quality
Software engineers create code quickly, sometimes cutting corners on documentation, which can lead to confusion and maintenance challenges on the documentation engineer's part.

Battle 4: Communication
Communication gaps about the technicalities of a new feature, the changes in a product, and the lack of context between software engineers and documentation engineers sometimes make life difficult for documentation engineers.

Battle 5: Who is more technical?
Sometimes, software engineers do not feel that documentation engineers are not technical enough, thus leading to conflicts.

Who wins the battles? Who wins the war? Who suffers at the end? I'll explore these concepts.