---
# System prepended metadata

title: dOrgJelli

---

# dOrgJelli

Jordan is one of dOrg and Polywrap founders. He worked very actively at dOrg for high profile clients like TheGraph, and DAOStack; being a key element in dOrg's early success. However, since the founding of Polywrap, he has dedicated less time to client work at dOrg. Nonetheless, he's still assisted rather recent client projects like Boardroom and hopped on to help on anything if the need arises.

Therefore, I am analyzing one of the last client projects Jordan led for a dOrg client: Arc.React. And I'm also discussing his contributions and role at Polywrap.

## Arc.React: In-depth analysis
### Statistics:

* Total lines: 6,800
* Contribution = 65.33%

### Automated analysis results:

- General assessment: https://sonarcloud.io/summary/overall?id=namesty_arc.react
- Main points of improvement: https://sonarcloud.io/component_measures?metric=reliability_rating&selected=namesty_arc.react%3Astorybook%2Fhelpers%2FPropertyEditors.tsx&view=list&id=namesty_arc.react

#### Conclusions and observations

- Reliability score is coming up as "C" but really there's a single "C" level bug detected. Not only that, it's already marked as noted and that should be fixed in the future (see TODO comments). Sonar's estimated fix time is about 20 minutes and doesn't really compromise the quality of the code
- All other scores are "A" which is great.
- No security vulnerabilities or breaches
- Small percentage of code duplication

### Human analysis results:

- It's a UI library and it uses Storybook; which is a tool for development, showcasing, testing and documenting UI components in isolation. This is a great plus.
- All components are tested
- Components API is documented
- Contains example applications to show usage

## Polywrap Toolchain: Contributions

### Contribution highlights:

- Jordan was the initial architect of Polywrap. He had the perspective and experise to see a need, imagine a solution and design it technically. Core concepts from Jordan's initial architecture still live in the current code (Wasm as means for secure portable execution, composability through Wasm module orchestration, MsgPack data translation, etc.). Here's the link to Polywrap's core toolchain so you can see his contributions, not only in commits/PRs but also in discussions and issues: https://github.com/polywrap/toolchain
- He's played a key leadership role in shaping the project's technical strategy over time. This has involved evaluating new technologies and tools, architectural changes, perspective and knowledge for weighing in on key decisions that impact the project's long-term direction.
- He orchestrated most of the development work management in the early stages of the project.
- He led the initial team that implemented Polywrap's first MVP to get funds for the long-term development of the project.
- He has implemented a significant part of the core features and functionalities; which entails: deep software architecture and computer-science knowledge, working with bleeding-edge technologies, scarce documentation and tools, etc. And as the project matured he's constantly refined and detected points of improvement which aren't simple or obvious (ex: https://github.com/polywrap/toolchain/issues/158).
- Jordan has figured ways of overcoming big technical challenges and limitations, even if refined later, async imports support is a great example: https://github.com/polywrap/toolchain/pull/29
- He's greatly mentored other Polywrap developers by sharing his perspective, helping with implementation blockers, helping others research, recording videos to teach or show how a certain technology or feature works, participating in pair programming sessions to help others, doing code review, etc. Ex: https://www.youtube.com/watch?v=7Py47nt__fg