• 5 Posts
  • 217 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle











  • I’m imagining a scenario where you’re working on a feature that changes the DB state (e.x. introduces a new DB migration that changes some columns) and the bug is on an unrelated part of the code from your feature. In this hypothetical, going back to the state of the upstream branch would make your local environment non functional, and the bug is on an unrelated part of the code. Fairly specific scenario but hey, you can worktree for that. It’s not particularly thorough, though.








  • And that’s really what all these guys saying “AI will take er jobs” don’t understand. Good programmers are not just good coders, coding is really the easy part. They’re also good analysts and listeners. I understand what he’s saying - if you spend time accruing specific domain knowledge instead of computer science then you can perhaps make better, bespoke solutions because the “coding” can be handled by AI. But in present day, AI makes garbage code all the time and you’ll be left there not being able to do amything about it because it doesn’t make any sense to you. So who do you call? Someone who can code. Even if we get to this hypothetical dream scenario where you tell an AI to do something and it just does it perfect (gigantic IF), who’s making that AI? The interface for it? The important safety nets to make sure it doesn’t go on a rampage? Itself? Too much context is already lost in conversations between humans, let alone an AI. I can think of one kind of AI that would be able to do it perfectly though (assuming AIs could be perfected, that is), and that’s an AI pre-equipped with full understanding of the domain. But then in that case, why do you need the human in the mix at all?