[josecodea]

Exactly! You are actually considering all the possible ways in which your approach might be wrong and in which the time would be wasted. You are assessing risk before you take action. You are analyzing the subtleties in communication, you determined that the wording relied on a lot of subjective vocabulary and you know that this leads towards misunderstandings. This is, in my humble opinion, the professional way of making decisions as a software engineer.

From reading the other comments, it seems like there are a lot of mind-readers among us. ¯\_(ツ)_/¯

[mplanchard]

I think it’s telling that the comments here are full of people noting mistakes that you made in your interpretation and/or execution, and rather than trying to learn from the experience, you appear to just be doubling down on your insistence that you’re entirely in the right.

Yes, there were flaws in the assignment and communication with the company, but there were also flaws in your approach. You’d be better off to try to take away some lessons here rather than blaming everyone but yourself.

Frankly, if I were you I’d consider deleting both your comments here and the blog post. I don’t think they reflect well on you as a candidate for future roles.

[jemiluv8]

Well said. The author of the blogpost is taking this all too personal. While also seemingly ignoring their own shortcomings in their approach. I'd see it more as a learning opportunity because there was clearly a huge gap in the intended interpretation of the take home and their own interpretation.

[jemiluv8]

> Frankly, if I were you I’d consider deleting both your comments here and the blog post. I don’t think they reflect well on you as a candidate for future roles.

That would be a wise move at this point. I keep wondering what the point of the post was?