Comments by "Brent Jacobs" (@br3nto) on "Can We Use AI To LEAD Software Development Teams?" video.

11:42 AI tools aren’t in the right place to achieve the goals that both of you are looking for. AI tools in the IDE is really the wrong place for them. Instead, they should be in git repositories and issue tracking systems. Then it could be the goal to define requirements, and have AI tools to help incrementally change the system to meet the requirements. People in the loop can validate or direct the changes. Requirements can incrementally change, and the AI tools identify and close the requirements gaps. Maybe even suggest 10 different alternatives for consideration. Devs can provide feedback on the alternatives, and combine the alternatives. Etc etc. there is still this fundamental problem of making sure that everyone is on the same page and working in the same direction and making the right changes though. The other gap is that we don’t have a cross-boundary multi-language “compiler” that can detect error states in distributed systems yet. That is , a compiler that can create an AST for any distributed or monolithic system.
2
5:35 I like that point Dave. What we actually want to know is: what are the gaps between what the system does and what we want the system to do, and what effort and cost is required to close those gaps. Leaders of organisations want to be able to steer the ship, and to do that they need to know how to correct course and what efforts and resources will get them to the new place quicker. Actually, it’s probably not just leaders that want that, rather everyone wants that.
1
The other point is that leadership teams often don’t really care about the small details of how. Their focus is more on things like: how can we increase our market share, how can we increase profit, how can we attract bigger customers with larger growth potentials, what market segment niches should we be expanding into or getting out of?
1