No. It's made me a much better and more effective programmer, by a huge amount.
I'd still be able to get stuff done without AI, and sometimes do, as a practice, but it'd be a drag.
Ask HN: Did AI make you a worse programmer?
11–14 of 14 posts
Re: Ask HN: Did AI make you a worse programmer?
#12Earlier quoted context omitted.
Obviously I didn't mean to imply that your merits as a programmer should be judged by your ability to recall specific syntax, like the equality operator in some language. I'm wondering about the long term effects of not paying attention to such details. Do you miss out on picking up patterns used by a certain library, framework, language or whatever, that you could have used to write your own code better?
Sometimes there are little details that increase risk if you don't pay attention to them. Like can't you use either "==" or "===" in Typescript but the first one can sometimes do a type coercion that can occasionally have unexpected effects? If I remember right it is a warning but not an error, a programmer who is clearing up warnings will stay out of trouble but if you weren't clearing warnings it would make a diffe…
[deleted]
Re: Ask HN: Did AI make you a worse programmer?
#13Earlier quoted context omitted.
Obviously I didn't mean to imply that your merits as a programmer should be judged by your ability to recall specific syntax, like the equality operator in some language. I'm wondering about the long term effects of not paying attention to such details. Do you miss out on picking up patterns used by a certain library, framework, language or whatever, that you could have used to write your own code better?
Sometimes there are little details that increase risk if you don't pay attention to them. Like can't you use either "==" or "===" in Typescript but the first one can sometimes do a type coercion that can occasionally have unexpected effects? If I remember right it is a warning but not an error, a programmer who is clearing up warnings will stay out of trouble but if you weren't clearing warnings it would make a diffe…
Hopefully there's a senior/staff engineer where you're at that actually knows the difference and is able to (find time to) comment on PRs where the wrong one is used. It's one of those "background radiation" things that you develop after working in a language for long enough.
Re: Ask HN: Did AI make you a worse programmer?
#14Earlier quoted context omitted.
Obviously I didn't mean to imply that your merits as a programmer should be judged by your ability to recall specific syntax, like the equality operator in some language. I'm wondering about the long term effects of not paying attention to such details. Do you miss out on picking up patterns used by a certain library, framework, language or whatever, that you could have used to write your own code better?
Sometimes there are little details that increase risk if you don't pay attention to them. Like can't you use either "==" or "===" in Typescript but the first one can sometimes do a type coercion that can occasionally have unexpected effects? If I remember right it is a warning but not an error, a programmer who is clearing up warnings will stay out of trouble but if you weren't clearing warnings it would make a diffe…
TypeScript on the strictest settings + aggressive ESLint rules is incredibly strict and a fantastic target for AI code. It's a good practice to have the CI/CD server reject code that fails ESLint anyway.