DEV Community

loading...

Discussion on: Interview Qs Decoded - # 2

Collapse
johannesjo profile image
Johannes Millan

Performance is one way to look at it, another is readability and ease of use. If you assume only reasonably short strings and a reasonable amount of iterations then I would argue that the easier readable solution is the better one, as it is inviting less misunderstandings and saves time every time a developer reads your code. Just mentioning that so you don't judge your interviewees prematurely only on performance ;)