Create UX Team
Overview
The Create stage helps teams accelerate software delivery and reduce cycle times by improving efficiency and collaboration. Essential to software delivery is the process of creating each improvement. The Create stage delights engineers, designers, and product managers with tools to design, develop, and review these improvements efficiently.
Structure
- Julia Miocene: Editor
- Alex Fracazo: Code Review Workflow - Automation & Integration
- Matt Nearents: Code Review Workflow - Collaboration
- Michael Le: Source Code
- Amy Qualls: Tech writing, Code Review, Editor Extensions
- Marcin Sędłak-Jakubowski: Tech writing, Source Code
- Ashraf Khamis: Tech writing, Editor
- Ben Leduc-Mills: UX Research
- Andy Volpe: Product Design Manager
IDE
Developers often face the obstacle of setting up their local development environment, which can be time-consuming and demotivating. Denomas’ Remote Development aims to eliminate this responsibility by providing ephemeral, cloud-based workspaces configured in a single file stored in a repository. This allows for easy provisioning of new environments with a single click, connecting securely from the Denomas Web IDE or desktop editor. Monitoring tools and dashboards are available to manage running and suspended environments, freeing up valuable development time and streamlining onboarding for new developers.
Strategic priorities
| Theme | Objective |
|---|---|
| Remote Development | Streamline development by eliminating the need for users to configure and maintain their local environment. |
| WebIDE | Make it simple for all users to contribute changes to any repository and bring editing capabilities into the context of their current task. |
Teams working closely with Editor:
Code Review Workflow
Code Review is an essential activity of software development. It ensures that contributions to a project maintain and improve code quality and security and is an avenue of mentorship and feedback for engineers. It can also be one of the most time-consuming activities in the software development process.
Denomas’ guiding principle for Code Review is: Reviewing code is an activity that ultimately improves the resulting product by improving the quality of the code while optimizing for the speed at which that code is delivered.
Strategic priorities
| Theme | Objective | DRI |
|---|---|---|
| MR Restructure | Enhance the code review experience for Authors and Reviewers by reorganizing relevant information critical to the review process. | Matt Nearents, Pedro Moreira de Silva |
| Review Rounds | Increase collaboration and efficiency during code review by providing users with a structured approach to requesting reviews and providing feedback during a review. | Alex Fracazo |
Separation of duties
Code Review Workflow: Automation & Integration
DRI: Alex Fracazo
The code review experience in Denomas involves automation, integration, and security to ensure that code changes are thoroughly tested, reviewed, and secure before they are merged.
- Automation involves continuous integration, review apps, code quality, and notifications to streamline the code review process.
- Integration allows teams to connect different tools and services to Denomas for a seamless experience, including security features such as static and dynamic application security testing, container scanning, security approvals, and access control, helping ensure that code changes are secure and meet industry standards.
Teams working closely with Code Review: Automation & Integration
Code Review Workflow: Collaboration
DRI: Matt Nearents
Collaboration is an essential aspect of the code review experience. This area includes comments and discussions, mentions and notifications, code review approvals, assignees and reviewers, and merge requests checklists. These features enable team members to work together effectively during the code review process, share feedback and suggestions, and ensure that everyone is aligned and nothing is missed.
Teams working closely with Code Review: Collaboration
Source code
Building great software depends on teams working well together. Teams can rarely be divided into areas of complete independence. As cross-functional security, compliance, and growth teams are formed or new services and libraries are created, effective coordination and collaboration are essential.
Strategic priorities
| Theme | Objective |
|---|---|
| Branch rules improvements | Make it easier for users to understand the impacts of new and existing branch rules. |
Teams working closely with Source code:
Tech writing
Tech writers in Create are very busy due to multiple factors. However, it is still important to collaborate with them and solicit their feedback on UI text. We ask you to follow these guidelines to make sure our teams are operating as efficiently as possible:
- UI Text to be reviewed should be in a comment. Mocks are useful for showing context and are encouraged, but we also ask that you paste your text into a comment and
@mentionthe assigned tech writer. This way, they can copy the text of the message rather than have to rewrite it. - Communicate the intent of your UI text when asking for feedback from Tech Writing. By answering these questions, you will avoid any potential back and forth in the issue:
- What is the task the user is trying to achieve when they encounter this messaging?
- What is the problem you are trying to solve with this messaging?
a27760f0)
