Can We Use AI To LEAD Software Development Teams?
1,161
Published 2024-08-11
Listen to the full episode HERE ➡️ open.spotify.com/episode/6I5ctJ8fawwV7ncN71N4vh?si…
-
🗣️ THE ENGINEERING ROOM PODCAST:
Apple - apple.co/43s2e0h
Spotify - spoti.fi/3VqZVIV
Amazon - amzn.to/43nkkRl
Audible - bit.ly/TERaudible
-
🙏The Engineering Room series is SPONSORED BY EQUAL EXPERTS
Equal Experts is a product software development consultancy with a network of over 1,000 experienced technology consultants globally. They increase the pace of innovation by using modern software engineering practices that embrace Continuous Delivery, Security, and Operability from the outset ➡️ bit.ly/3ASy8n0
-
#softwareengineer #developer
All Comments (10)
-
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.
-
incrementalism - perfect point! :medal-yellow-first-red:
-
The person that made this up should get a patent on no managerial vision.
-
Fortunately for a seasoned dev or experienced lead dev, AI does not replace experience, your most valued asset. It tends to not offer solutions to a broad understanding of the codebase and tech stack or platform. It offers a solution to a prompt or a narrowly scoped immediate problem.
-
9:23 Isn't that what's called temperature in the OpenAI API? If you set that to 0 you get reproducible results.
-
answer is no?
-
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.
-
A lot of talking but no answer to the question ?
-
No
