Critical thinking and communication, as the mantra goes, are key to success. These concepts are frequently touted for their benefits in many different fields, but for documenting code to be maintained for years, they are quintessentially essential.
As always, the book explains it in an eloquent way:
“As developers, we have to communicate on many levels. We spend hours in meetings, listening and talking. We work with end users, trying to understand their needs. We write code, which communicates our intentions to a machine and documents our thinking for future generations of developers. We write proposals and memos requesting and justifying resources, reporting our status, and suggesting new approaches. And we work daily within our teams to advocate our ideas, modify existing practices, and suggest new ones. A large part of our day is spent communicating, so we need to do it well.”
Almost all of my experience so far has been on personal projects, but these are traits which can be built upon and developed. For my upcoming systems and software principles group projects, I’ll make sure these basic points are applied to the documentation and requirements.
That concludes day 6. See you tomorrow!
#PathToSWE
