▲ | belval 2 days ago | ||||||||||||||||||||||||||||||||||||||||||||||
I was in a lovely meeting where a senior "leader" was looking at effort estimates and said "Do these factor in AI-tools? Seems like it should be at least 30% lower if it did." Like I use AI tools, I even like using them, but saying "this tool is so good it will cut our dev time by 30%" should be coming from the developers themselves or their direct manager. Otherwise they are just making figures up and forcing them onto their teams. | |||||||||||||||||||||||||||||||||||||||||||||||
▲ | scrumper 2 days ago | parent [-] | ||||||||||||||||||||||||||||||||||||||||||||||
I was that manager. I dunno about your senior leader but with me it was coming from a healthy place. After a few months of ra-ra from the C suite about how we were now an AI-first company (we're a tech consultancy building one-off stuff for customers) and should be using it in all our customer projects, I asked the question, quite reasonably I thought, "so am I going to offer lower prices to my clients, or am I going to see much higher achieved margins on projects I sell?" And, crickets. In practice I haven't seen any efficiencies despite my teams using AI in their work. I am not seeing delivery coming in under estimates, work costs what it always cost, we're not doing more stuff or better stuff, and my margins are the same. The only difference I can see is that I've had to negotiate a crapton of contractual amendments to allow my teams to use AI in their work. I still think it's only good for demos and getting a prototype up and running which is like 5% of any project. Most technical work in enterprise isn't going from zero to something, it's maintaining something, or extending a big, old thing. AI stinks at that (today). You startup people with clean slates may have a different perspective. | |||||||||||||||||||||||||||||||||||||||||||||||
|