Sign in with Facebook
Mark Richards’s Followers (13)
Mark Richards
More books by Mark Richards…
“Pay close attention to developer flow and be sure not to disrupt it by calling a meeting. Flow is a state of mind developers frequently get into where the brain gets 100% engaged in a particular problem, allowing full attention and maximum creativity. For example, a developer might be working on a particularly difficult algorithm or piece of code, and literally hours go by while it seems only minutes have passed. When calling a meeting, an you should always try to schedule meetings either first thing in the morning, right after lunch, or toward the end of the day, but not during the day when most developers experience flow state.”
― Fundamentals of Software Architecture: An Engineering Approach
― Fundamentals of Software Architecture: An Engineering Approach
“A control freak architect might restrict the development team from downloading any useful open source or third-party libraries and instead insist that the teams write everything from scratch using the language API. Control freak architects might also place tight restrictions on naming conventions, class design, method length, and so on. Essentially, control freak architects steal the art of programming away from the developers, resulting in frustration and a lack of respect for the architect.”
― Fundamentals of Software Architecture: An Engineering Approach
― Fundamentals of Software Architecture: An Engineering Approach
“Meetings that an architect imposes upon others (the architect calls the meeting) are also a necessity at times but should be kept to an absolute minimum. These are the kinds of meetings an architect has control over. An effective software architect will always ask whether the meeting they are calling is more important than the work they are pulling their team members away from. Many times an email is all that is required to communicate some important information, which saves everyone tons of wasted time.”
― Fundamentals of Software Architecture: An Engineering Approach
― Fundamentals of Software Architecture: An Engineering Approach
Is this you? Let us know. If not, help out and invite Mark to Goodreads.
