Yea. And I would consider that amateurish. Especially considering the fact that you can absolutely prompt them to look at it from different angles. Imo devs should spend 80% of their time looking at block diagrams and call stacks and thinking about what can go wrong. How they can design fallbacks, proactively design against failures, optimize speed etc. The implementing of the actual loops and helper functions is not nearly as important as understanding how pieces fit together and ensuring that they perform as expected both individually and when combined.

A lot of parts of nostr are like that. Frustrating. Devs need to agree on a more intensive review policy for nips. Especially before it gets added to the quote-unquote official list.