Teams, in software engineering, form because of success. Without success, the firm wouldn’t be cursed with the problem of having so much talent to have to organize in some way. A founder can easily reduce the complexity in their human organization, and their lives, by simply not hiring any more than seven technologists to work with them on their mission. For some, this is viable. For others, this is not. Teams emerge in response to scale. They are either formed as by product of centralized hierarchical command structure, or they emerge as a product of network cohesion/polarization. To the extent that either formation is aligned with the vision, goal, mission, or purpose of the organizational chrome is a function of[…]
Tag: software
Imagine with me: what if novels were written like software. Sometimes it’s useful to approach absurdity and look inside. There might be treasure there. I’ll define software as an executable, a set of instructions, that are interpreted by a machine for some reason. As a data scientist, I think of software as a product, and I think, constantly, of turning data into product. I think of data as inertia and all the code around it as flexible. I worry a lot about the people that use the software (if anybody) and think of them as heterogenous segments. I think of a novel as an executable, a set of instructions, that are interpreted by a human brain for some reason. As[…]