this post was submitted on 13 May 2026
60 points (96.9% liked)
Asklemmy
54433 readers
322 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 7 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm still writing 90% of my code by hand at work. I think if you have total or close to total mastery in your domain, you should probably work faster than AI.
It takes a while for AI to generate code (Opus is pretty slow) and then you have to go review it and do rounds and rounds of fixes. It might be faster to use AI if there were unknowns or if you werent quite sure how to write the code. Otherwise I just find it faster to write it myself.
That being said I do use AI under some soecific circumstances:
For 1. And 2. I dont usually have ai write code for me. I would just ask it questions like "how do I write X in an idiomatic way in language Y".
For 3, I have it generate code that I then toss and rewrite if the prototype works.
For 4, this is rare in a good code base. Most of the boiler plate heavy code at work is in unit tests.
I've been wary of all those use cases. If I'm unfamiliar with the code base, the language, or have a vague plan then I focus on getting understanding first; AI gives false confidence and I can't check it's work if I don't understand what I'm doing. I've never written much boilerplate code as I use templates, written by humans, when starting a new project. The idea of starting from a slop codebase isn't appealing as you need a good foundation.
The problem I find is it can take a year or longer before you learn what is idiomatic and what isn't and it's not always obvious. You can ask colleges of course but it can slow down development drastically if you need to ask often. Most times, you don't have the luxury of practicing the language for a year before you ship code so you can use AI to get a general sense of what is best practice in that language. Worst case if AI gets it wrong, it will get caught in review.
As for understanding code bases, I'm working in code bases with millions of lines of code. Before AI I would usually ask someone to point me in the general vicinity or spend 30 minutes trying to find the right ballpark to look at for a particular thing. With AI, it can usually find it in 5 minutes or less. I still learn where the code lives if I need to reference it again in the future so I don't really see much of a downside here other than that I get to save a chunk of time from having to pore through hundreds of source files.