Earlier quoted context omitted.
[dead]
Skill issue. If you make an effort to use the new tools effectively, the gains are wild. Don't fall into a grumpy luddite trap, the train is leaving the station and you'll struggle to catch up if you don't learn and grow. Not using AI for software development in 2027 will be like only knowing how to program via punchcard in 2010. It's new. It's different. It's hard. It's your job. Learn how to use it effectively, emb…
AI usage patterns in software teams
111–120 of 154 posts
Re: AI usage patterns in software teams
#112Earlier quoted context omitted.
> Usage does not correlate with valued output or ROI This sounds possible but how can we know? It could just as well correlate. Effort of all kinds correlates with success even when it's not obvious or not... linear.
[dead]
Sure, you could say all digital transformations are nebulous snake oil and don't deliver but I just don't think this is the case.
Re: AI usage patterns in software teams
#113Earlier quoted context omitted.
I program as a hobby, personal projects because I can. I recently set up a local llm to see what the fuss is about and other than the few ringer solutions my experience is as you described. 2min promping, 5min waiting, 3hrs debugging or just doing it myself. I am very likely doing it wrong, and it does speed up some aspects, but I wouldn't say I trust llm code any more than my own. Until it runs and throws an error,…
Local llms aren’t super exciting unfortunately.
Re: AI usage patterns in software teams
#114Earlier quoted context omitted.
No, don’t be silly, they get ai to spy on you en masse instead. Nobody has to look at anything anymore for it to be actionable.
Absolutely, have warned my juniors of this. Doesn't stop malicious compliance though, I can just prompt and burn tokens with source material from my assigned tickets for no reason perfectly fine. I look at my colleagues' screens and they're prompting shit like 'restart this program' and 'is [service] running correctly'. I have below average prompt frequency because I know crazy shit like #!/bin/bash and ps aux. It's…
Re: AI usage patterns in software teams
#115Earlier quoted context omitted.
[dead]
Skill issue. If you make an effort to use the new tools effectively, the gains are wild. Don't fall into a grumpy luddite trap, the train is leaving the station and you'll struggle to catch up if you don't learn and grow. Not using AI for software development in 2027 will be like only knowing how to program via punchcard in 2010. It's new. It's different. It's hard. It's your job. Learn how to use it effectively, emb…
Re: AI usage patterns in software teams
#116Usage does not correlate with valued output or ROI. This article smells like a bad attempt to say hey guys our customers see ROI without any actual evidence that they do. Also, somewhat amusingly, the “founder” consistently being at the top of the use curve might just have something to do with everyone else also using it, but that more implies people are using it because the chief at the top wants them to use it… not…
[dead]
Re: AI usage patterns in software teams
#117Re: AI usage patterns in software teams
#118Earlier quoted context omitted.
Skill issue. If you make an effort to use the new tools effectively, the gains are wild. Don't fall into a grumpy luddite trap, the train is leaving the station and you'll struggle to catch up if you don't learn and grow. Not using AI for software development in 2027 will be like only knowing how to program via punchcard in 2010. It's new. It's different. It's hard. It's your job. Learn how to use it effectively, emb…
>> Don't fall into a grumpy luddite trap, the train is leaving the station and you'll struggle to catch up if you don't learn and grow. If that's true things are truly hopeless for pre-school/school children who are not in position to jump on the train just yet.
Re: AI usage patterns in software teams
#119Earlier quoted context omitted.
Writing code directly takes longer to warm up. Usually, I'd keep tens of thousands of lines in my head. In the past, I spent a lot of time designing error propagation and execution contexts. (Talented people might figure it out right away, but unfortunately I don't have that kind of talent.) So I'd have to think about things like Result and how far to propagate errors—and worry about whether my approach would conflic…
> But these days, AI just generates code following the existing patterns of the codebase Is this sarcasm?
Re: AI usage patterns in software teams
#120Earlier quoted context omitted.
I tried hard to tokenmaxx one month and couldn’t do it as for most tasks, I’ve already figured out the solution while reading the ticket and vim/emacs-fu is more enjoyable than prompting and waiting. And for other tasks, I just knew the technology to do something with the least amount of effort.
[dead]