From 03a8f37bd0e30705025c0f21bfe933fc73633df8 Mon Sep 17 00:00:00 2001 From: Vadim <1125014+zolotokrylin@users.noreply.github.com> Date: Mon, 26 Feb 2024 16:20:26 +0800 Subject: [PATCH 01/13] Update README.md resolves https://github.com/holdex/hr/issues/102 --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index bcf5baa..111c235 100644 --- a/README.md +++ b/README.md @@ -7,6 +7,7 @@ This is where your Holdex journey starts. Make sure to align yourself with: - [Contributing Guidelines](./.github/CONTRIBUTING.md) - [Sick Leave Policy](https://holdex.io/c/learn/leave) +- [Compensation Guide](https://holdex.io/c/learn/compensation-guide) ## For HR - message templates are located here: [/templates](./templates) From 0b26bcddbe8fa0c30373342ce447cf2231eb1192 Mon Sep 17 00:00:00 2001 From: Vadim <1125014+zolotokrylin@users.noreply.github.com> Date: Mon, 26 Feb 2024 16:59:12 +0800 Subject: [PATCH 02/13] add overlapping time --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 111c235..4c09b1a 100644 --- a/README.md +++ b/README.md @@ -9,5 +9,7 @@ Make sure to align yourself with: - [Sick Leave Policy](https://holdex.io/c/learn/leave) - [Compensation Guide](https://holdex.io/c/learn/compensation-guide) +> ![IMPORTANT] Most of the team members working from the remote location. However, we expect everyone to overlap work hours between 2-6 PM HKT daily. + ## For HR - message templates are located here: [/templates](./templates) From cad132cc296d469150b1cdf3c3c15bfba05b0dc9 Mon Sep 17 00:00:00 2001 From: Vadim <1125014+zolotokrylin@users.noreply.github.com> Date: Mon, 26 Feb 2024 18:15:56 +0800 Subject: [PATCH 03/13] Update README.md --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 4c09b1a..a87b166 100644 --- a/README.md +++ b/README.md @@ -9,7 +9,8 @@ Make sure to align yourself with: - [Sick Leave Policy](https://holdex.io/c/learn/leave) - [Compensation Guide](https://holdex.io/c/learn/compensation-guide) -> ![IMPORTANT] Most of the team members working from the remote location. However, we expect everyone to overlap work hours between 2-6 PM HKT daily. +> [!IMPORTANT] +> Most of the team members working from the remote location. However, we expect everyone to overlap work hours between 2-6 PM HKT daily. ## For HR - message templates are located here: [/templates](./templates) From 6c9fedf502696a794e09b136df46dc2ef9d7d7cf Mon Sep 17 00:00:00 2001 From: Vadim <1125014+zolotokrylin@users.noreply.github.com> Date: Mon, 26 Feb 2024 18:16:48 +0800 Subject: [PATCH 04/13] Update README.md --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index a87b166..38c60e4 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,8 @@ Make sure to align yourself with: - [Compensation Guide](https://holdex.io/c/learn/compensation-guide) > [!IMPORTANT] -> Most of the team members working from the remote location. However, we expect everyone to overlap work hours between 2-6 PM HKT daily. +> Most of the team members working from the remote location. +> However, we expect everyone to overlap work hours between 2-6 PM HKT daily. ## For HR - message templates are located here: [/templates](./templates) From 379c52270b3d855c325c42a6edafdee96e5a54d2 Mon Sep 17 00:00:00 2001 From: Vadim Date: Fri, 7 Nov 2025 14:15:53 +0800 Subject: [PATCH 05/13] docs: assign reviewer to PR Signed-off-by: Vadim --- .github/CONTRIBUTING.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index ec5d839..52ea037 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -77,7 +77,7 @@ Different problems may require different sets of skills. Whether it’s code, design, or marketing material, we expect a lean and clean solution from the contributor. > [!NOTE] -> Solution is presented in GitHub as [Pull Requests (PR)](https://docs.github.com/en/pull-requests) in compliance with [PR Requirements](#pr-requirements). +> Solution is presented in GitHub as a [Pull Request (PR)](https://docs.github.com/en/pull-requests) in compliance with [PR Requirements](#pr-requirements). ### Referencing @@ -151,9 +151,10 @@ The required checks are as follows: ## Drafting -When start working on a Problem, you must open a [draft PR](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests#draft-pull-requests) right away. Do not mark PR as "ready to review" unless you are confident it is ready. - -When creating a PR, you must [link it](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword) to the corresponding Problem (issue). +When starting to work on a Problem, you must: +1. Open a [draft PR](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests#draft-pull-requests) right away. Do not mark PR as "ready to review" unless you are confident it is ready. +2. [Link opened PR](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword) to the corresponding Problem (issue). +3. Before marking your PR as ready for review, assign **at least one reviewer** (team or individual). Do not merge without approved review. ### Design PRs From b0ea6f4e4d5836f8b1d4b24033205b0cf3bc3184 Mon Sep 17 00:00:00 2001 From: Vadim Date: Fri, 7 Nov 2025 14:31:37 +0800 Subject: [PATCH 06/13] docs: view compensation guide Added a comprehensive compensation guide outlining principles, expectations, and team culture for various roles. Signed-off-by: Vadim --- .github/COMPENSATION.md | 63 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 63 insertions(+) create mode 100644 .github/COMPENSATION.md diff --git a/.github/COMPENSATION.md b/.github/COMPENSATION.md new file mode 100644 index 0000000..031a6c9 --- /dev/null +++ b/.github/COMPENSATION.md @@ -0,0 +1,63 @@ +# Compensation guide + +Compensation principles and the expectation we have from our team members + +At Holdex, everybody contributing to the business should be treated and rewarded equitably, regardless of where they come from, how old and `experienced` they are, or what titles they have been assigned. It all may seem essential, but it doesn’t give you superpowers. It’s all about having the [right attitude](https://holdex.io/c/learn/principles) and the positive impact you can make. We established 2 fundamental rules to achieve it: + +* Clear incentives . All salaries and bonuses are based on a simple merit system. The more you contribute by independently delivering end results, the more rewards you will receive. Doing the same job at the same level is paid the same regardless of location or other factors. +* Resilient framework . One that’s simple, consistent, and universally adhered to—without exceptions. A framework that can help people grow inside the team and help them understand what is expected from them. + +> Check our open job positions if you are looking for challenges and new opportunities, or you are as excited for [our mission](https://holdex.io/about) as we are, check our [open job positions](https://holdex.io/c/jobs). + +## Our approach + +To help everyone on our team understand what is expected of them and where they can improve, we put together a framework decomposed into traits that we regularly track. Not just for developers but for everyone: designers, finance, strategy, partnership, customer relations, etc. + +### Team culture + +| | Entry | Intermediate | Lead | Principal | +| -- | -- | -- | -- | -- | +| Align yourself with [our missions, vision, and values](https://holdex.io/about) | ✅ | ✅ | ✅ | ✅ | +| Respect [our principles](https://holdex.io/c/learn/principles) and [guidelines](https://holdex.io/c/learn/github-strategy) and remind them to your teammates | ✅ | ✅ | ✅ | ✅ | +| Inspire, coach and lead team members in a project | ❌ | ❌ | ✅ | ✅ | +| Improve existing values, principles, rules, frameworks | ❌ | ❌ | ❌ | ✅ | + +### Goals + +| | Entry | Intermediate | Lead | Principal | +| -- | -- | -- | -- | -- | +| Understand / Align with goals | ✅ | ✅ | ✅ | ✅ | +| Decompose goals into problems | ❌ | ✅ | ✅ | ✅ | +| Research and provide the solution to the goals | ❌ | ✅ | ✅ | ✅ | +| Define goal timelines and blockers | ❌ | ❌ | ✅ | ✅ | +| Ensure goal achievement | ❌ | ❌ | ✅ | ✅ | +| Identify business goals | ❌ | ❌ | ❌ | ✅ | +| Define correct priority and value to the goal | ❌ | ❌ | ❌ | ✅ | + +### Problems & Solutions + +| | Entry | Intermediate | Lead | Principal | +| -- | -- | -- | -- | -- | +| Provide solutions for the Problems | ✅ | ✅ | ✅ | ✅ | +| Estimate the solution and follow it | ✅ | ✅ | ✅ | ✅ | +| Research independently | ✅ | ✅ | ✅ | ✅ | +| Interview stakeholders | ✅ | ✅ | ✅ | ✅ | +| Present solution to the stakeholders | ✅ | ✅ | ✅ | ✅ | +| Bug-free execution | ❌ | ✅ | ✅ | ✅ | +| Identify real problems | ❌ | ✅ | ✅ | ✅ | +| Break down problems into sub-problems | ❌ | ✅ | ✅ | ✅ | +| Define correct priority and value | ❌ | ✅ | ✅ | ✅ | +| Assist Entry team members | ✅ | ✅ | ✅ | ❌ | +| Review solutions implemented by other team members | ❌ | ✅ | ✅ | ❌ | +| Delegate and distribute problems to the best fitting member | ❌ | ❌ | ✅ | ✅ | + +## Looking forward + +A startup studio like Holdex has so many processes that we can’t put them all in a framework (although, we’d love that, haha). Some of them are hard to pack or to remember. Others get blurry and overlap constantly. Yet, we managed to add a bit of structure and expand more on our expectations from each level to help you figure out which areas to grow. + +| | Our expectations from you | +| -- | -- | +| Entry | * Execute solutions to the problems.
* Be an excellent student eager to learn new things from more advanced team members.
* Ability to research for the necessary information independently.
* Explore and start mastering a strong point of view.
* Clearly communicate and explain your work to other people.
* Improve your skills but also master new things, like presenting to clients, understanding strategy, understanding the business side of things, etc.
* Be humble and don’t take feedback personally. It’s about solving the problem, and it is not about you.
* Expose yourself to the business part of things. Be aware of constraints, client dynamics, and business needs. | +| Intermediate | * Great execution and great confidence.
* Identify real business and technical Problems.
* Figure Solutions to complex Problems yourself.
* Articulate your point of view with perfection.
* Become a trusted partner of the Lead and Principal.
* Adapt to every situation and challenge. Comfortable with discomfort.
* Develop leadership skills.
* Great communication skills with stakeholders.
* Leave your ego and collaborate with others (designers, strategists, stakeholders, devs, and so on) to make the project amazing.
* Inspire others. Become someone our Entry members look up to. Be generous and motivate them.
* Help Entry members grow. Help entry members when they are stuck.
* Be comfortable with being on the business side of things. (discussing timelines, partnerships, 3rd party integrations aligning with stakeholders on the values of certain things )
* Look up to the next level. Will to become a Lead. | +| Lead | * Leading a project (as a primary person) from start to finish.
* Capable of stepping in for your Principal when he is missing.
* Be a clear delegator and distribute workload across your team members.
* Praise your team’s efforts.
* Be able to join the action and show amazing crafting skills when needed.
* Become more of a coach than a player with full responsibility for the work being done.
* Display great ideas, great solutions, understand the strategy and the business processes of the customer and our company.
* Able to zoom in-and-out: from ideas and execution to big-picture strategy.
* Have very strong point of view but open to other people’s ideas too.
* No ego. Best collaborative attitude because it’s not about you anymore. It’s about leading.
* Be inspiring, solid and precise in meetings with clients and your team.
* Lead by example and make everyone on the team feel safe. They should look up to you.
* Participate in business discussions. Apply your vision over a project to define timelines and budgets, requirements etc.
* Have full perspective over a project, remain accountable and connect with everyone on the team and with the client. | +| Principal | * Less hands-on and more brains-on.
* Be prepared to jump into the pitch and collaborate with team members directly.
* Own multiple projects of any size at the same time. Starting from the initial strategy to release celebration.
* Bring your strong point of view and develop passion in others
* Decode customer feedback and translate it to the team members in actionable items.
* Don’t micromanage.
* Let your team take the credit. They are probably more skilled.
* Improve team culture.
* Business is your second language. Understand all aspects of a project. Other teams and partners are your best friends.
* Help find new business opportunities for the company.
* Become the trusted partner of our customers.
* Be able to say NO to customers when they need to hear it.
* Be able to adapt to any situation or turn of events from customers, teams and business. | From 42a1f70a7f715323b78ce2be6ca6fad656fb6830 Mon Sep 17 00:00:00 2001 From: Vadim Date: Fri, 7 Nov 2025 14:39:06 +0800 Subject: [PATCH 07/13] docs: follow the link to Compensation Guide Signed-off-by: Vadim --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index c76ddc8..e5df205 100644 --- a/README.md +++ b/README.md @@ -10,5 +10,6 @@ Align with: - [Contributing Guidelines](./.github/CONTRIBUTING.md) - [DOs & DON'T](.github/DONTS.md) - [Sick Leave Policy](./.github/LEAVE_POLICY.md) +- [Compensation Guide](./.github/COMPENSATION.md) Subscribe to repository notifications to stay updated with frequent fixes and improvements. From 3b3d89dc041e738de54ccd97c3532f19c053b189 Mon Sep 17 00:00:00 2001 From: Vadim Date: Fri, 7 Nov 2025 14:52:10 +0800 Subject: [PATCH 08/13] docs: view simplified version Signed-off-by: Vadim --- .github/COMPENSATION.md | 76 +++++++++++------------------------------ 1 file changed, 20 insertions(+), 56 deletions(-) diff --git a/.github/COMPENSATION.md b/.github/COMPENSATION.md index 031a6c9..9dce8df 100644 --- a/.github/COMPENSATION.md +++ b/.github/COMPENSATION.md @@ -1,63 +1,27 @@ -# Compensation guide +# Compensation Guide -Compensation principles and the expectation we have from our team members +**Goal:** Reward impact, not titles or location. Pay based on merit—what you deliver independently. -At Holdex, everybody contributing to the business should be treated and rewarded equitably, regardless of where they come from, how old and `experienced` they are, or what titles they have been assigned. It all may seem essential, but it doesn’t give you superpowers. It’s all about having the [right attitude](https://holdex.io/c/learn/principles) and the positive impact you can make. We established 2 fundamental rules to achieve it: +> Open roles: [holdex.io/c/jobs](https://holdex.io/c/jobs) | Mission: [holdex.io/about](https://holdex.io/about) -* Clear incentives . All salaries and bonuses are based on a simple merit system. The more you contribute by independently delivering end results, the more rewards you will receive. Doing the same job at the same level is paid the same regardless of location or other factors. -* Resilient framework . One that’s simple, consistent, and universally adhered to—without exceptions. A framework that can help people grow inside the team and help them understand what is expected from them. +## Core Rules +1. **Clear incentives** — Same job, same level = same pay. More results = more rewards. +2. **Simple framework** — Consistent rules for growth. -> Check our open job positions if you are looking for challenges and new opportunities, or you are as excited for [our mission](https://holdex.io/about) as we are, check our [open job positions](https://holdex.io/c/jobs). +## Levels & Core Skills -## Our approach +| Level | Key Traits & Expectations | Team Culture | Goals | Problems & Solutions | +|-------|---------------------------|--------------|-------|----------------------| +| **Entry** | Student mindset: Bug-free. Execute tasks. Research. Learn fast. Communicate clearly. Take feedback. | Follow [principles](https://holdex.io/c/learn/principles) & [GitHub rules](https://holdex.io/c/learn/github-strategy). | Understand goals. | Solve, estimate, research, present. Help juniors. | +| **Intermediate** | Confident executor: Solve complex problems. Lead small parts. Help Entry. Strong opinions. | Follow principles. Remind team. | Break into problems. Research solutions. | Identify real problems. Break down. Prioritize. Review juniors. | +| **Lead** | Project owner: Run full projects. Delegate. Coach team. Align with business. Inspire. | Coach others. Lead in projects. | Set timelines. Ensure delivery. | Delegate. Distribute to best fit. | +| **Partner** | Big-picture leader: Own multiple projects. Shape strategy. Say no when needed. Grow culture. | Improve rules/values. | Define business goals & priorities. | (All above + strategic input) | -To help everyone on our team understand what is expected of them and where they can improve, we put together a framework decomposed into traits that we regularly track. Not just for developers but for everyone: designers, finance, strategy, partnership, customer relations, etc. +## Growth Path -### Team culture - -| | Entry | Intermediate | Lead | Principal | -| -- | -- | -- | -- | -- | -| Align yourself with [our missions, vision, and values](https://holdex.io/about) | ✅ | ✅ | ✅ | ✅ | -| Respect [our principles](https://holdex.io/c/learn/principles) and [guidelines](https://holdex.io/c/learn/github-strategy) and remind them to your teammates | ✅ | ✅ | ✅ | ✅ | -| Inspire, coach and lead team members in a project | ❌ | ❌ | ✅ | ✅ | -| Improve existing values, principles, rules, frameworks | ❌ | ❌ | ❌ | ✅ | - -### Goals - -| | Entry | Intermediate | Lead | Principal | -| -- | -- | -- | -- | -- | -| Understand / Align with goals | ✅ | ✅ | ✅ | ✅ | -| Decompose goals into problems | ❌ | ✅ | ✅ | ✅ | -| Research and provide the solution to the goals | ❌ | ✅ | ✅ | ✅ | -| Define goal timelines and blockers | ❌ | ❌ | ✅ | ✅ | -| Ensure goal achievement | ❌ | ❌ | ✅ | ✅ | -| Identify business goals | ❌ | ❌ | ❌ | ✅ | -| Define correct priority and value to the goal | ❌ | ❌ | ❌ | ✅ | - -### Problems & Solutions - -| | Entry | Intermediate | Lead | Principal | -| -- | -- | -- | -- | -- | -| Provide solutions for the Problems | ✅ | ✅ | ✅ | ✅ | -| Estimate the solution and follow it | ✅ | ✅ | ✅ | ✅ | -| Research independently | ✅ | ✅ | ✅ | ✅ | -| Interview stakeholders | ✅ | ✅ | ✅ | ✅ | -| Present solution to the stakeholders | ✅ | ✅ | ✅ | ✅ | -| Bug-free execution | ❌ | ✅ | ✅ | ✅ | -| Identify real problems | ❌ | ✅ | ✅ | ✅ | -| Break down problems into sub-problems | ❌ | ✅ | ✅ | ✅ | -| Define correct priority and value | ❌ | ✅ | ✅ | ✅ | -| Assist Entry team members | ✅ | ✅ | ✅ | ❌ | -| Review solutions implemented by other team members | ❌ | ✅ | ✅ | ❌ | -| Delegate and distribute problems to the best fitting member | ❌ | ❌ | ✅ | ✅ | - -## Looking forward - -A startup studio like Holdex has so many processes that we can’t put them all in a framework (although, we’d love that, haha). Some of them are hard to pack or to remember. Others get blurry and overlap constantly. Yet, we managed to add a bit of structure and expand more on our expectations from each level to help you figure out which areas to grow. - -| | Our expectations from you | -| -- | -- | -| Entry | * Execute solutions to the problems.
* Be an excellent student eager to learn new things from more advanced team members.
* Ability to research for the necessary information independently.
* Explore and start mastering a strong point of view.
* Clearly communicate and explain your work to other people.
* Improve your skills but also master new things, like presenting to clients, understanding strategy, understanding the business side of things, etc.
* Be humble and don’t take feedback personally. It’s about solving the problem, and it is not about you.
* Expose yourself to the business part of things. Be aware of constraints, client dynamics, and business needs. | -| Intermediate | * Great execution and great confidence.
* Identify real business and technical Problems.
* Figure Solutions to complex Problems yourself.
* Articulate your point of view with perfection.
* Become a trusted partner of the Lead and Principal.
* Adapt to every situation and challenge. Comfortable with discomfort.
* Develop leadership skills.
* Great communication skills with stakeholders.
* Leave your ego and collaborate with others (designers, strategists, stakeholders, devs, and so on) to make the project amazing.
* Inspire others. Become someone our Entry members look up to. Be generous and motivate them.
* Help Entry members grow. Help entry members when they are stuck.
* Be comfortable with being on the business side of things. (discussing timelines, partnerships, 3rd party integrations aligning with stakeholders on the values of certain things )
* Look up to the next level. Will to become a Lead. | -| Lead | * Leading a project (as a primary person) from start to finish.
* Capable of stepping in for your Principal when he is missing.
* Be a clear delegator and distribute workload across your team members.
* Praise your team’s efforts.
* Be able to join the action and show amazing crafting skills when needed.
* Become more of a coach than a player with full responsibility for the work being done.
* Display great ideas, great solutions, understand the strategy and the business processes of the customer and our company.
* Able to zoom in-and-out: from ideas and execution to big-picture strategy.
* Have very strong point of view but open to other people’s ideas too.
* No ego. Best collaborative attitude because it’s not about you anymore. It’s about leading.
* Be inspiring, solid and precise in meetings with clients and your team.
* Lead by example and make everyone on the team feel safe. They should look up to you.
* Participate in business discussions. Apply your vision over a project to define timelines and budgets, requirements etc.
* Have full perspective over a project, remain accountable and connect with everyone on the team and with the client. | -| Principal | * Less hands-on and more brains-on.
* Be prepared to jump into the pitch and collaborate with team members directly.
* Own multiple projects of any size at the same time. Starting from the initial strategy to release celebration.
* Bring your strong point of view and develop passion in others
* Decode customer feedback and translate it to the team members in actionable items.
* Don’t micromanage.
* Let your team take the credit. They are probably more skilled.
* Improve team culture.
* Business is your second language. Understand all aspects of a project. Other teams and partners are your best friends.
* Help find new business opportunities for the company.
* Become the trusted partner of our customers.
* Be able to say NO to customers when they need to hear it.
* Be able to adapt to any situation or turn of events from customers, teams and business. | +| Level | Focus | +|-------|-------| +| **Entry** | Learn → Execute → Ask | +| **Intermediate** | Solve → Teach → Lead small | +| **Lead** | Own → Delegate → Coach | +| **Partner** | Strategize → Scale → Say No | From 424502326696e919325aef1de4d70a2b72066365 Mon Sep 17 00:00:00 2001 From: Vadim Date: Fri, 7 Nov 2025 15:03:03 +0800 Subject: [PATCH 09/13] docs: view Principles Signed-off-by: Vadim --- .github/PRINCIPLES.md | 44 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 .github/PRINCIPLES.md diff --git a/.github/PRINCIPLES.md b/.github/PRINCIPLES.md new file mode 100644 index 0000000..6b9f799 --- /dev/null +++ b/.github/PRINCIPLES.md @@ -0,0 +1,44 @@ +# Our Principles + +**We build great things together—fast, smart, and with full ownership.** + +## The 6 Rules We Live By + +1. **Start with the Goal** + Keep the big picture. Break it into clear problems. Solve one at a time. + +2. **Own It Like a Founder** + No one assigns tasks. You spot problems, claim them, and deliver results. + +3. **Ship Daily, Small & Often** + No task >4 hours. Finish, push, move on. Momentum beats perfection. + +4. **Respect Time—Yours & Others** + One team sync/week. Work async. No meetings unless needed. + +5. **Wear Many Hats** + Code, design, test, write, explore. We grow by doing. + +6. **Figure It Out** + Research. Read. Ask. Learn fast. No waiting for instructions. + +--- + +## Do This | Not That + +| ✅ **Do** | ❌ **Don’t** | +|----------|-------------| +| Solve what moves the goal | Work on low-value tasks | +| Own it end-to-end | Pass the buck | +| Test your work | Expect others to QA | +| Leave clear updates | Vanish without trace | + +--- + +## ⏰ Core Hours +**2–6 PM HKT** — Be online. Rest is flexible. + +--- + +**Be bold. Be fast. Be kind.** +That’s how we win. From 5e960af9e7c6bb1aa6d7f94ebfb5c29f3bfbfe9e Mon Sep 17 00:00:00 2001 From: Vadim Date: Fri, 7 Nov 2025 15:05:08 +0800 Subject: [PATCH 10/13] Fix link formatting in README.md Signed-off-by: Vadim --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index e5df205..54d8d24 100644 --- a/README.md +++ b/README.md @@ -7,6 +7,7 @@ Your journey to shape the future starts here. _Developers_ are everyone creating value—business developers, designers, engineers, marketers, and beyond. We build businesses, products, partnerships, customer relationships, processes, and delivery methods, crafting the future we envision. Align with: +- [Principles](./.github/PRINCIPLES.md) - [Contributing Guidelines](./.github/CONTRIBUTING.md) - [DOs & DON'T](.github/DONTS.md) - [Sick Leave Policy](./.github/LEAVE_POLICY.md) From 5b9b11706b1f494ea7b9e93f835b7e3f076e29ab Mon Sep 17 00:00:00 2001 From: Vadim Date: Fri, 7 Nov 2025 15:08:01 +0800 Subject: [PATCH 11/13] Delete .github/DONTS.md Signed-off-by: Vadim --- .github/DONTS.md | 25 ------------------------- 1 file changed, 25 deletions(-) delete mode 100644 .github/DONTS.md diff --git a/.github/DONTS.md b/.github/DONTS.md deleted file mode 100644 index ed690b6..0000000 --- a/.github/DONTS.md +++ /dev/null @@ -1,25 +0,0 @@ -# ✅ DOs and ❌ DON'Ts - -These guidelines are key to working effectively as a team. We've learned them through experience, so follow them to avoid common mistakes. - ---- - -## ✅ DOs -- **Align with Goals**: Keep the big picture in mind and break goals into smaller, actionable tasks for clarity and focus. -- **Focus on What Matters**: Work on tasks that directly contribute to our goals. -- **Take Ownership**: Tackle challenges head-on, and if you're stuck, communicate your difficulties with the team. -- **Overlap Work Hours**: Be available between 1–6 PM HKT daily to collaborate effectively. -- **Test Thoroughly**: Ensure your work is reliable and well-tested before marking it complete. -- **Leave Updates**: Share progress frequently through comments or commits, ideally on an hourly basis. -- **Value Time**: Respect others’ time. Work independently but collaborate when needed. Avoid relying on others for things you can handle yourself. -- **Wear Many Hats**: Embrace versatility—code, design, test, write, and explore ideas because we're passionate about building great products. -- **Be Resourceful**: Learn independently by exploring documentation, tutorials, and using tools like AI to find solutions. - ---- - -## ❌ DON'Ts -- **Engage in Low-Value Work**: Avoid tasks that don't meaningfully contribute to our goals. -- **Avoid Responsibility**: Take accountability for your tasks and challenges. -- **Neglect Testing**: Don’t rely on others to test your work for you. -- **Disappear Without Updates**: Keep the team informed—don’t make others chase you for progress. -- **Distract Others**: Avoid unnecessary or irrelevant messages. Share only what’s important and helpful to collaborators. From 80d3e8a892a72938233586be4546b6faa9b7a858 Mon Sep 17 00:00:00 2001 From: Vadim Date: Fri, 7 Nov 2025 15:08:17 +0800 Subject: [PATCH 12/13] Remove DOs & DON'Ts link from README Removed link to DOs & DON'Ts from the README. Signed-off-by: Vadim --- README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/README.md b/README.md index 54d8d24..7adebde 100644 --- a/README.md +++ b/README.md @@ -9,7 +9,6 @@ _Developers_ are everyone creating value—business developers, designers, engin Align with: - [Principles](./.github/PRINCIPLES.md) - [Contributing Guidelines](./.github/CONTRIBUTING.md) -- [DOs & DON'T](.github/DONTS.md) - [Sick Leave Policy](./.github/LEAVE_POLICY.md) - [Compensation Guide](./.github/COMPENSATION.md) From e3edd8dab4526c336a7bc1aa8bc80e48d510f670 Mon Sep 17 00:00:00 2001 From: Vadim Date: Fri, 7 Nov 2025 15:08:56 +0800 Subject: [PATCH 13/13] Update welcome message in README.md Signed-off-by: Vadim --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7adebde..5fdfd63 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,5 @@ # Developer Guidelines -Welcome to the Developer Guidelines! +Welcome to our Developer Guidelines! Your journey to shape the future starts here. ## For Developers