jmartrican
Joined 9 years ago
Karma
1,028
Submissions
500
Member since
May 6
Joined 9 years ago
Now lets talk about factuality. A human creator can just as easily lie or not fact-check all their sources. But if they do decide to fact-check, wouldn't it be easier to just task the AI to fact check. Simply tell it, "leave out any data that has not been fact checked and mapped back to a reliable source."
1) A lot of the time i spent deciding on interfaces (methods, classes, etc.) for humans. E.g. should this be two methods or one, should this method be in this class or moved to utility. Those problems went away. 2) What about performant code? This can be prompted away and when the measurements in your performance tests do not go down, then you can step in. 3) Sad to say but the AI has always been better than me at code-reviews. Maybe this is just me and if so I own that, but to the articles point, it might be harder to fix now. 4) "vibe-coded projects devolve over time into an unmaintainable mess". Preventing and managing this mess is the new skill sets we need to develop as software engineers. 5) Another skill-set we will need to master is how to maintain and grow our coding skills. Some ideas are: a) every once in a while implement a feature yourself. b) no AI Tuesdays! c) Have the AI quiz you on the code base. d) Have the AI develop HTML docs about how the code works.