Clarifying requirements, designing architecture. Also, I dont understand how is someone supposed to be able to “parse code” without being able to write it? It’s like being able to read but unable to write.
I can read significantly more programming languages than I can write working code in. You can usually figure out the syntax and get the gist of what’s going on in a non trivial amount of code. Sure, the oddball syntax/language feature comes up that I have to lookup but it’s not too bad.
Well I never mentioned I was responsible for doing a review of someone else’s code in a language I don’t know. That would be foolish. There are plenty of open source projects that have lack luster documentation. Reading the code is really the only way to figure out how it works sometimes.
ditto, similar to the way Severence gets a sense of whats off, i cna do that with code, ask me to start from scratch i would not know where to start. Give me google, i will have a bunch of a copy pasta that works in the end, claude does the research, evaluation, best practices and review and testing and re-review and testing, when the Developers department will go to war with you if you put a Slack question through the wrong channel
I understand cooking concepts and can tell when something I am familiar with is made well. If I watch a cook, most of the time I can tell why they do certain things anand how it impacts the food.
My cooking skills are very limited, especially when it comes to making new things. My sql skills are the same, I can read through the code and spot errors that match issues, but even creating something new is fairly limited despite being able to read and comprehend what has already been done.
Clarifying requirements, designing architecture. Also, I dont understand how is someone supposed to be able to “parse code” without being able to write it? It’s like being able to read but unable to write.
I can read significantly more programming languages than I can write working code in. You can usually figure out the syntax and get the gist of what’s going on in a non trivial amount of code. Sure, the oddball syntax/language feature comes up that I have to lookup but it’s not too bad.
So really what you do is guess what the code you read is doing. Which is generally fine.
But how can you be sure in a review that the code will actually work? How can you falsify it? A review is more than just reading code.
Well I never mentioned I was responsible for doing a review of someone else’s code in a language I don’t know. That would be foolish. There are plenty of open source projects that have lack luster documentation. Reading the code is really the only way to figure out how it works sometimes.
ditto, similar to the way Severence gets a sense of whats off, i cna do that with code, ask me to start from scratch i would not know where to start. Give me google, i will have a bunch of a copy pasta that works in the end, claude does the research, evaluation, best practices and review and testing and re-review and testing, when the Developers department will go to war with you if you put a Slack question through the wrong channel
That’s not enough for production code.
Besides, this just reads like what a kid does with a Lego.
thats all code is to me, I just wish it would stop telling me I am no true Scotsman
FORTRAN inline for loops go brrrrrr
I understand cooking concepts and can tell when something I am familiar with is made well. If I watch a cook, most of the time I can tell why they do certain things anand how it impacts the food.
My cooking skills are very limited, especially when it comes to making new things. My sql skills are the same, I can read through the code and spot errors that match issues, but even creating something new is fairly limited despite being able to read and comprehend what has already been done.