# Joshjack Joshjack is a long-standing member of dOrg that has participated in important projects like Zer0. His most relevant recent work has been for closed-source projects. In this case, I could have him walk me through the architecture and codebase of Concrete; the latest project he's worked on with dOrg. He's been one of the main architects and smart contract developer of the project. ## Concrete: In-depth analysis Concrete is a risk-protocol for lenders ### Human analysis results #### Positive highlights: - Overall, I was very impressed with the professional, organized and formal way he handled his role, the relationship with the client, the requirements and technical aspects of the project, etc. - Showed a very deep understanding of the technical requirements of the project - Condensed his knowledge and understanding of the requirements in formal technical documentation (using Gitbook), UML diagrams and other visual resources to better guide the rest of the team; and have an easier time navigating the architecture with the client - He transformed the requirement and knowledge into tasks that could be distributed among the team members - He was given a certain degree of freedom to design the required solution, as the project was built from the ground up. His solution was clear, easy to understand, clever and approved/liked by the client. - He came up with important parts of the architecture on his own, and he walked me through the business logic that led to it - He created a variation of the ERC-1155. He walked me through the rationale and implementation details with ease - The smart contract patterns and data structures he used looked correct and understandable - Performed code review for the contributions of other members - Client's feedback was greatly positive #### Points of improvement: To be honest, with this kind of orgnization, documentation, formality and commitment; errors, even if they existed, could be detected in a timely manner and handled. So I don't think I have points of concern. This tech leadership was clear, and text-book good. This is the ideal tech lead behavior IMO.