At Atomic the software consultant & developers are product innovators, tool sharpeners, process geeks and, of course, skilled developers.
We've recently begun to introduce "Developer Archetypes," a set of self-identified labels Atoms can use to radiate their strengths and interests.
The highest priority of a software team's Delivery Lead is to make sure the team isn't blocked, keeping everybody in sync, marching toward the product goal.
Recently, I needed to create a web app and ended up choosing Next.js. Although the Next.js framework was new to me, I found a lot of things to like.
Our short-handed management model requires us to hire the right people, foster the right culture, provide process, and to have positive support structures.
Integrated design/development backlogs are a great way of coordinating tasks, but integrated burn charts are another story.
When our teams are divided, we forget about the big picture and lose time. Communication is the key to keeping us together.
Teams of generalist software makers are more efficient, more profitable, and more successful than teams of specialists.
It's not their fault, but your talented departements are inclined to suffocate your innovative efforts.
Insights as to how developers practice design and an assertion of the diminishing value of the "coder" mindset.
Scott Page's book: The Difference: How the Power of Diversity Creates Better Groups, Firms, Schools, and Societies offers a compelling argument for diversity as a powerful force fo
Poly-skilled co-located teams of generalists are more likely to deliver products on time and efficiently than separate groups of specialized people.