-2
Ask Lemmy: What do you currently use for AI coding?
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 07 Jun 2026
-2 points (48.9% liked)
Programming
27201 readers
223 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
Not remembering specifics of a technology, and completely forgetting the base building blocks - the same blocks that you should be using for AI generated code too, BECAUSE YOU NEED TO FUCKING REVIEW IT - is not the same.
I'm an Android engineer by trade. I might not be able to give you the exact interface definition of a BroadcastReceiver, or explain in technical terms the core differences between a TextureView and a SurfaceView (that's what the documentation is for!), but for sure as hell can tell you if your architecture is good or not, or if the quality of the code you wrote is shite.
If I can't remember a specific interface I can not judge if would be the right tool for the given job. Using suboptimal tools is bad architecture for me.
That's just a simple example.
It took me about 8 weeks to get back up to my old productivity, and suddenly code that looked perfectly fine from agent backed project's give me nightmares.
Not remembering an interface is easily alleviated.
Forgetting core architectural principles - which are the cornerstone of good architecture - cannot be fixed that easily.
Micro details, specifics, are what the docs are for. You don't need to remember the specifics as long as you have the understanding of what the thing does.
Macro details - appropriate information and event pipelines, SOLID, KISS, etc., are what architecture is about. You can write the best micro-scope code if the end result on a macro level is spaghetti that would feed Rome for a year.