They knew nobody else had done it for them here the second they hit a single issue.
Why not step back at that point and try to understand the entire problem you may be facing?
This like people who build software by just fixing one bug they see at a time by trying to make the compiler happy or whatever, instead of stepping back and thinking about the system as a whole - what other assumptions are likely wrong if you had this bug?
Worse, here there was a very easy solution: Ask questions before you start.
Just because it's common for software developers to not bother to ask people for knowledge they don't have doesn't mean it's a good answer.
They knew nobody else had done it for them here the second they hit a single issue.
Why not step back at that point and try to understand the entire problem you may be facing?
This like people who build software by just fixing one bug they see at a time by trying to make the compiler happy or whatever, instead of stepping back and thinking about the system as a whole - what other assumptions are likely wrong if you had this bug?
Worse, here there was a very easy solution: Ask questions before you start.
Just because it's common for software developers to not bother to ask people for knowledge they don't have doesn't mean it's a good answer.