5 ms·
Even all that, difficult though it is, doesn't include the cost if understanding the actual problem, knowing the field well enough to propose a good solution, a
by webnrrd2k 3y ago
Even all that, difficult though it is, doesn't include the cost if understanding the actual problem, knowing the field well enough to propose a good solution, and coordinating and communicating with everyone the whole way through.
"Every problem is a people problem", and people-solutions are something that AI still doesn't solve.
I'm not saying that AI doesn't have it's uses, it certainly does, but I'm trying to highlight that purely technical solutions very often aren't good solutions to a lot if real-world problems.
- worldsayshi 3y agoWhen AI truly becomes helpful in the workplace developer jobs will probably change a lot but I think the biggest change will be in the size of the business scope. Most projects I've worked in could easily grow ten times if developers were ten times as efficient. At the same time I've always wondered why IT problems haven't all been solved comprehensively already because so many problems seem so similar. I can't really fit those two narratives together.
- pixl97 3y agoAll IT problems are 90% similar... it's the last 10% difference that is 9000% of the work! I think part of the problem is human networking limitations. I can learn to code very well and can become a core contributor on a project. The problem is my understanding doesn't scale well. If I get hit by a bus tomorrow that project could die. I could leave the project and it could flounder. Now, lets say you add 3 people as good as me on that project... the problem is the project will grow 4 times as large leading to every one of us becoming a critical failing point. Any time you want to bring a new core contributor in, it's a massive undertaking of time and effort to get them up to speed.
- worldsayshi 3y agoYeah this rhymes with my experience. AI could perhaps turn this dynamic on its head if we let it into all the code bases. Now it can perhaps explain the background for all the nooks and crannies in the code. It could chip into any discussion in the corporate or community environment to tell you why another team has designed the way they've done. It can potentially act as a mediator to make a more cohesive whole. But that all also kind of sounds a bit scary. It has to be built in a way that inspires trust.