4 ms·
Which might make you, what, maybe 10% more productive overall? The more experienced you are, the less time you spend writing boilerplate code, so it's not that
by RussianCow 3y ago
Which might make you, what, maybe 10% more productive overall? The more experienced you are, the less time you spend writing boilerplate code, so it's not that huge of a win in the grand scheme of things compared to what it provides when you're learning something new.
- koonsolo 3y agoNot writing any unit tests are you?!?!? ;)
- anonzzzies 3y agoIt makes us far more productive; all of us, so we just do more as a team rather than fire someone. For me, copilot writing out if / then / else stuff like it's reading my mind, so tab -> 15 lines, all correct. Or mappings (.map .filter etc) which it completely does within milliseconds. As an experienced programmer, I cannot avoid these things and they do save me a lot of time and debugging. Oh yes, and tests. Going from a jira task to a bunch of jest tests for code that doesn't exist yet is a pretty big win. Very much more than 10% of the average day. You have to be sharp, be a good code reader and writer and it cannot do anything 'alone', but it makes us vastly more efficient.
- raincole 3y ago> Which might make you, what, maybe 10% more productive overall? The more experienced you are... But the more exeperienced you are, more valuable your output is (in most cases). So the 10% of your productivity could be more valuable than a novice's 50%.
- tuyiown 3y agoThe more experience you are, the less the value is in the output objective productivity. The ability to write self descriptive, maintainable and bitrot resistant code in one pass goes way above feature delivery.