10 years of coding exp and clearly asked: "it should be easy to async/parallel stuff, right?"
To which someone, pasted that fairly small example of a channel read/ write. Based on your own reading, you can tell if that is easy for you or not. But, I do agree with the original response, which also could be taken as a dip stick if he is ready to start working with concurrency.
I myself focus on the readibility of an example when asked from a beginner. Because I want them to not have a bad starting experience with a language. No matter how many years of experience they have, they still might not know what differ does in Go. Or when you're using go func () {} () inside another func that makes the code less readable. That's why they said: "give me back my async await syntax", because there are distractions in the code that the OP doesn't know the meanings of, my point is those distractions that phsycologically trick our mind that such code is hard. And I believe this doesn't matter if you have 1 year or 10 years of experience in general programming field. Reading the book "Clean Code" made me realize that.
That's fair 👍
Обсуждают сегодня