Writers without a strong developer background struggle with Git. Part of the problem is that the basic metaphors don’t apply to distributed systems. There’s no “bucket” of “your” stuff. Git changes your view depending on a number of factors, and once you understand them without relying on metaphors from centralized source control systems, you’ll really understand what happens when you change a file and submit it to the system. Fear will become confidence.
Git provides fantastic review and commenting ability, stellar forensics, and far better conflict resolution than typical technical writing tools. But you can’t take advantage of these unless you can use Git with confidence.
-2017 STC TechComm Summit program
About the presenter
Principal Technical Writer
I fix the content problems that nobody else can or will. After 25 years in the industry, I have deep experience with technical documentation for enterprise software, helping companies as diverse as Sybase and 20th Century Fox.
Specialties: XML authoring (DITA/OpenToolkit), structured authoring, content strategy, content modeling, Database (Sybase, Oracle), Java IDE (JDeveloper), web services, SOA. API, user guide, reference guides, developer guides, internal documentation, and architecture documentation. Concise and friendly, my work always supports user goals.
— Nominated for several salesforce.com internal awards, one a team award in 2014.
— Screenwriter with several awards.
— Short story writer with several awards.
— Finished with my first fraud investigator/mystery novel, By The Numbers.