3 ms·
Kind of like "please describe the solution and I will write code to do it". That's not how programming works. Writing code and testing it against expectations t
by cratermoon 2y ago
Kind of like "please describe the solution and I will write code to do it".
That's not how programming works.
Writing code and testing it against expectations to get to the solution, that's programming.
- mathgeek 2y agoLanguage is important here. Programming, at its basic definition, is just writing code that programs a machine. Software development or even design/engineering are closer to what you’re referring to.
- brandonchen 2y agoFWIW I don't find that I'm losing good engineering habits/thought processes. Codebuff is not at the stage where I'm comfortable accepting its work without reviewing, so I catch bugs it introduces or edge cases it's missed. The main difference for me is the speed at which I can build now. Instead of fussing over exact syntax or which package does what, I can keep my focus on the broader implications of a particular architecture or nuances of components, etc. I will admit, however, that my context switching has increased a ton, and that's probably not great. I often tell Codebuff to do something, inevitably get distracted with something else, and then come back later barely remembering the original task