undefined | Better HN

0 pointstokioyoyo5d ago0 comments

For my team, it has been easy. We deal with infrastructure for the entire org, so have tickets created for every request. We also gave our own backlog for internal project, so can see burn rate, and etc. Team hasn’t changed, a lot of similar/same tasks that have taken half a day has been completely automated to a point where we just do PR review after an initial ticket is created by other teams.

There are a lot of little things we’ve tracked, and it’s just faster to implement things now. To be fair, everyone on my team has decade+ professional experience (many more non-prodessional), and we understand limitations of AI fairly well.

0 comments

djhn5d ago

What kind of code is infrastructure in this context? Devops in a software company? Internal tooling in a software org?

intended5d ago

Thank you for sharing any info at all.

> to be fair, everyone on my team has decade+ professional experience (many more non-prodessional), and we understand limitations of AI fairly well.

I see this appear quite often in discussions on productivity, to the point that a conclusion may be made regarding its centrality for productivity gains.

rubendev5d ago

What is your definition of faster to implement? Is it producing a plausible implementation, or is it faster at producing a correct and high quality implementation? Are you including time spent refactoring and fixing bugs in your metrics? If not, I think you are tracking a gut feeling rather than cold hard facts. I’m not saying this is easy to track, just saying that it’s hard to know for sure that you are really more productive with AI.

j / k navigate · click thread line to collapse