Areas of Impact

Now that I’m immersed in a career focused on coding and software creation, I can clearly see the benefits of my writing background. In a typical week, I allocate approximately 60% of my time to coding, 15% to meetings, 10% to learning through reading, and the remaining 15% to writing documentation and workflows.

While it may appear that writing skills are only applicable during the documentation phase, I've found that they permeate much more of my work. The ability to articulate my thoughts on paper enhances my capacity to organize my ideas mentally. This exercise encourages me to think critically before speaking and helps me slow down before sharing my work with the world.

This meticulous thought process is crucial in software development. When the functionality of our code isn't clearly defined, users may interact with it in unexpected ways, leading to workarounds for unresolved issues.

Planning and Revising

When embarking on a new project, I always begin by outlining the steps, milestones, and anticipated challenges. This strategy allows me to break my workload into manageable tasks, providing natural pauses where I can step back or brainstorm new ideas without losing my flow.

The editing phase has also refined my ability to be concise in my communication. I can pinpoint critical issues that need addressing for project advancement and highlight significant business decisions for future consideration, all while creating notes that serve as reference points for further elaboration.

Writing has also expanded my ability to think about the bigger picture. While drafting an article, I contemplate the essential components, the points requiring more depth, and what can be omitted to maintain coherence. This cognitive process parallels the planning stage in software development, where I can start with a Minimum Viable Product (MVP) and evolve it as necessary, ensuring that the final product aligns with user needs.

Communication

When creating documentation, I go beyond mere instructions, integrating the reasoning behind decisions, the problems the project addresses, and the alternatives considered. While reviewing legacy code, I often question why certain decisions were made, as understanding the rationale can illuminate insights that enhance future work.

By producing documentation that contextualizes the code, my team and I can better navigate the complexities of software development. This understanding not only clarifies current practices but also fosters an environment where improvement becomes second nature.

In essence, development is inherently collaborative, even if that collaboration is between you and your future self. It's vital not to rely solely on memory for crucial decisions and processes.

The crux of the matter is that programmers can gain significantly from engaging in activities outside of coding, whether it's playing an instrument, writing essays, or participating in sports. This cross-disciplinary training invariably enriches our core skills. Ultimately, the goal should be to develop problem-solving abilities; programming languages are simply tools in our toolkit, not the sole focus.