Trial: 0xcoreblock

[zolotokrylin]

I’d appreciate any guidance on how we can proceed for the next step.

Originally posted by @0xcoreblock in #684

[zolotokrylin]

@0xcoreblock, you have authors the following PRs:

• feat(ui): view Jakobs endorsement link in Portfolio Page holdex-venture-studio#685
• chore(ui): replace link component for same styled a tag as link holdex-venture-studio#692

What went wrong

Code Quality and Reviews

You got many rejects.

Aim for solutions that work correctly 99.9% of the time. Be independent and thorough in your QA - reviewers are not QA team members but are there for a final safety check. We expect contributors to deliver bug-free software, understanding that perfection is an ideal. Stand firm in your solutions and avoid unnecessary revisions based on subjective feedback.
Ref: https://github.com/holdex/developers/blob/main/.github/CONTRIBUTING.md#code-quality-and-reviews

Code of Conduct
...
2. Ensure the quality of your work. It is a sign of poor ownership and lack of confidence when you expect someone to deal with your incomplete work.
Ref.: https://github.com/holdex/developers/blob/main/.github/CODE_OF_CONDUCT.md#code-of-conduct

What went well

You are proactive.

What's next

We cannot tolerate constant rejections. However, given your proactive approach, I can offer you the opportunity to open and merge another pull request (PR) where you take full responsibility for quality. It's important that this process doesn't consume too much of your peers.

We need independent contributors who can work asynchronously, merge quickly, and deliver solutions to business problems without creating operational challenges for others. Your goal should be to keep things simple for your colleagues and avoid complicating their work.

[zolotokrylin]

cc: @markholdex leaving this issue on you. P.S. Refer to the above reply; let's keep it as a standard of our replies to all candidates.