The Human Dimension of Software Engineering
This doodle went on for several meetings throughout the span of several days. It started in the center and expanded outward. You can tell the difference in styles and patterns at the various stages.
Do you enjoy Doodle Tuesday? Let me know what you think.
Building software is still in its infancy. Today we write a line of code at the time to describe what we believe a machine should do to resolve a problem. Developers spend most of their time sorting out minute details of behaviors. They do so to ensure that a task is executed precisely in a well-defined and understood way.
The unfortunate reality is that this method doesn’t scale well. The world needs software, but today’s software creation process is slow and complex. We’ve seen this in the past with other forms of art and craft. ...
Coding alone and coding in a team are two very different activities. Often people do not realize how quickly the complexity of teamwork explodes as the number of people increases. If you struggle to see the benefits of a development process, or if you have never thought about the productivity of teams of different sizes, this article is for you.
Thinkers such as Jeff Sutherland, Taiichi Ohno, and Kent Beck designed different forms of production processes to organize and tame team interaction complexities. Those processes form a body of well-defined frameworks that can be used to manage the flow of communication, providing a method to synchronize interactions between team members and attempting to create some predictability of the team’s output. ...
I rarely doodle in colors, but this time I had the right pens at the right time.
Another meeting doodle on the theme of threes, roots, and growth.
