How Many CTOs?

Should companies build or buy software factory dashboards?

Short answer

Companies face the dilemma of building or buying software factory dashboards. Building offers customization but can be resource-intensive, while buying provides ready-made solutions that may not fit all needs.

Companies face the dilemma of building or buying software factory dashboards. Building offers customization but can be resource-intensive, while buying provides ready-made solutions that may not fit all needs.

The Case for Building

Building a software factory dashboard allows for full customization to meet specific organizational needs. This approach is particularly appealing when existing solutions don't align with the unique processes or scale of a company. Brad shared an example from the episode where one of their engineers created a dashboard for his factory agents. This dashboard was impressive, showing ticket statuses, agent activities, and system metrics. However, it raised the question of whether everyone should be building their own or if a unified solution would be more efficient ▶ 9:37.

Scott noted that many developers have already created their own versions, which suggests a gap in the market for a one-size-fits-all solution. "Everybody is like building their own thing and it's fun," Scott said, highlighting the creative freedom and learning opportunities that come with building ▶ 11:01.

The Case for Buying

On the other hand, buying a software factory dashboard can save significant time and resources. Ready-made solutions often come with support and updates, reducing the burden on internal teams. Brad mentioned how big tech companies like Uber and others have developed their own factory UIs, but these are not available for purchase, leaving smaller companies to fend for themselves ▶ 12:04.

The challenge with buying is finding a product that fits all needs. Scott pointed out that while there are many IDEs available, people often customize them heavily, suggesting that even purchased solutions require significant adaptation. He drew parallels to IDEs like VS Code, which thrive on extensibility and customization ▶ 20:23.

Balancing Customization and Efficiency

The decision to build or buy often hinges on a company's specific needs and resources. Brad and Scott discussed how there seems to be a lack of a clear leader in the dev tool space, which might be due to the diverse requirements of different software development life cycles. Scott suggested that the Kanban board could serve as the UI for software factories, as it has traditionally been used to track work ▶ 0:00.

Brad raised concerns about whether this model scales effectively with agent-driven workflows. He noted that some companies have moved away from traditional tools like Git due to scalability issues, as the volume of changes can overwhelm conventional systems. "It's a little bit like the pull request," Brad mentioned, highlighting the challenges of scaling existing tools to meet the demands of modern software factories ▶ 22:05.

The Future of Software Factory Dashboards

As technology evolves, so too will the tools we use to manage it. Brad and Scott speculated that the future might involve more integrated solutions, where dashboards are part of a broader ecosystem of tools, possibly centered around chat-based interfaces. Brad mentioned how he uses chat interfaces to manage coding tasks, suggesting that this could be the direction for future dashboard solutions ▶ 32:56.

Scott shared an anecdote about attempting to create a personal assistant named "Isaac" to manage tasks through natural language interactions, further blurring the lines between traditional dashboards and conversational interfaces. This approach reflects a shift towards more personalized and interactive tools that adapt to individual workflows ▶ 33:44.

Conclusion

Whether to build or buy a software factory dashboard is a decision that depends on the specific needs and capabilities of a company. Building offers customization and control, while buying provides convenience and support. As the landscape of software development continues to change, companies must weigh these options carefully, considering both current needs and future possibilities. The conversation between Brad and Scott highlights the complexity of this decision, as well as the potential for innovation in this space.

In their words

Scott put it this way: "The UI for the factory is the Kanban board." ▶ 0:00. Brad reflected on the customization potential: "Yeah, anybody now can build their version of it, right?" ▶ 18:48.