it can be a fine edge to balance between short and expressive or becoming so short its cryptic instead. But less lines of code generally removes the risk of bugs hiding in the forest of characters on the screen, so I'm of the opinion that you should aim to keep things as short as possible, as long as it stays easy to read. And if it's new vocabulary, short functions with clear names should help anyone new to it to quickly understand what it does.
@@davidmurphy563 you're mistaking your understanding of the word, "fallacy" for "logical fallacy". Fallacy does not necessarily imply "logical fallacy" when it's used. Fallacy can just mean mistake or error.
It really depends. There are some coders who just love to use syntactic sugar all over the place. Sometimes all cramped in 1 line. No comment, no explanation in the function description, etc. this can be read and understood, but you have to deconstruct it. Not very ideal. You might as well show the generated/optimized binary. There are a lot of functions that I don't know here and keywords, but with my years of experienced coupled with the different languages I've learned I can figure out what the yield does and the other, what looks like, lambdas do. Sometimes using language features can be done incorrectly. For example doing something similar in C# would work perfectly assuming you're working with an enummerable. But if this, I believe is TS, doesn't have that concept then the code big O is much longer than expected. So yes obviously agree that it helps to know the language good, but also not to clog it all up in one line either or even 2 lines what should be broken down and use meaningful variables vs xyz, abc, etc
I agree with you , as a uni student i try to use programming techniques before writing my code , i try to use dynamic programming and divide & conquer so that i have more control on my code ، but again i had to search alot about how to write clean code and more controlled code , because they don't teach or mention this in uni
it can be a fine edge to balance between short and expressive or becoming so short its cryptic instead.
But less lines of code generally removes the risk of bugs hiding in the forest of characters on the screen, so I'm of the opinion that you should aim to keep things as short as possible, as long as it stays easy to read.
And if it's new vocabulary, short functions with clear names should help anyone new to it to quickly understand what it does.
I know replete + fallacy, however the lower sentence has fewer syllables and is therefore more efficient, and the sentence I prefer.
@@davidmurphy563 you're mistaking your understanding of the word, "fallacy" for "logical fallacy".
Fallacy does not necessarily imply "logical fallacy" when it's used. Fallacy can just mean mistake or error.
thank you for this
It really depends. There are some coders who just love to use syntactic sugar all over the place. Sometimes all cramped in 1 line. No comment, no explanation in the function description, etc. this can be read and understood, but you have to deconstruct it. Not very ideal. You might as well show the generated/optimized binary. There are a lot of functions that I don't know here and keywords, but with my years of experienced coupled with the different languages I've learned I can figure out what the yield does and the other, what looks like, lambdas do. Sometimes using language features can be done incorrectly. For example doing something similar in C# would work perfectly assuming you're working with an enummerable. But if this, I believe is TS, doesn't have that concept then the code big O is much longer than expected.
So yes obviously agree that it helps to know the language good, but also not to clog it all up in one line either or even 2 lines what should be broken down and use meaningful variables vs xyz, abc, etc
writing simple code comes from experience. new programmers normally produce spaghetti code.
I agree with you , as a uni student i try to use programming techniques before writing my code , i try to use dynamic programming and divide & conquer so that i have more control on my code ، but again i had to search alot about how to write clean code and more controlled code , because they don't teach or mention this in uni
Step 1: Remove typescript
Step 2: Make it simple enough for people to understand
Meh, it's js. No matter what you do it's ugly.