3 ms·
Speaking for our org, but it's because most business logic in our backends is about the same level or more complicated than String.contains.
by foobarian 5y ago
Speaking for our org, but it's because most business logic in our backends is about the same level or more complicated than String.contains.
- throwanem 5y agoIs it, though? I think real cases might frequently be less complicated, in Java at least. As is evident from the candidate experiences that the original commenter describes, there's a lot more complexity in strings than is immediately obvious. I agree with 'Gunax that that's likely to be tripping people up - as I mentioned in the comment to which you're replying, albeit in a somewhat recent edit, this has not nothing to do with why our own similar interview problems don't revolve around any operation on strings.
- foobarian 5y ago> Is it, though? You have no idea :-) Oh how I wish it were not the case