![]() When you focus on technical communication excellence, better engineering becomes a natural byproduct of the process. When a writer starts asking what software features do, how the system is organized, the purpose and benefits of the design, etc., all in an effort to document what’s there, the engineers who created the technology start seeing their own code in a new light, and improvements happen organically. But there’s a certain magic that happens when a tech writer is brought on board to clean up, complete, and standardize internal documentation. And in many cases, code and process documentation is nothing more than a collection of notes that individual engineers jot down to keep track of their own efforts. It’s typically written by the development teams themselves. Why? Because software documentation is commonly an afterthought. ![]() How many software industry professionals draw the connection between better engineering and their internal documentation? Spoiler alert: The answer is far too few. But reaching promised levels of efficiency and improvement has proven challenging for many organizations. Better engineering might also mean the adoption of modern software architectures, such as containers and microservices, running on highly scalable cloud architectures. Accelerated development and smaller releases mean faster production of features that customers want with fewer defects. ![]() What comes to mind when you hear the words better engineering? For many in the software industry, engineering improvements mean optimizing DevOps.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |