|
|
|
|
|
|
by padjo
1202 days ago
|
|
|
Curious, have you tried Co-pilot? The type of thinking and typing it saves me from are not trivial. It turns writing the remainder of a method into just pressing tab. Or completely writes test cases based on the case name. Or just suggests test cases entirely. The other day I let it autocomplete methods in a public interface and it was literally ideating feature ideas for me. Sure there’s overblown hype but there is also real value here. |
|
|
I'll try it for the sake of this conversation but I think it still doesn't change my point about being intentional and thinking.
I'd like to see examples of those tests. After many years of software development and seeing how many people produce buggy services that create a lot of maintenance burden or simply solve the wrong problem, I firmly believe writing is a minuscule part of the day and it's mostly about thinking enough and communicating well with the human interfaces of your project.
Writing is easy. You can get fast with touch typing or autocomplete features (including the copilot one) but that's not the most important thing.
Knowing why you do something and being able to analyze that decision after a period of time and evaluate how "right" it was, is not something that can be done for you.
For quick brainstorming it can be great but we should be careful with the authority we assign it to, when we can't really explain its thought process