From 90e8c6ef45d1723e6bbe81ab64ff5d8db38eed04 Mon Sep 17 00:00:00 2001 From: Vadim Date: Wed, 16 Apr 2025 10:46:54 +0800 Subject: [PATCH 1/6] docs: do this and don't do that Signed-off-by: Vadim --- .github/DONTS.md | 64 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 64 insertions(+) create mode 100644 .github/DONTS.md diff --git a/.github/DONTS.md b/.github/DONTS.md new file mode 100644 index 0000000..bd57ce7 --- /dev/null +++ b/.github/DONTS.md @@ -0,0 +1,64 @@ +As part of our team, it's essential to align yourself with these principles. +Both values and principles serve as the foundation for approaching our responsibilities and interacting with each other. In uncertain moments, our principles help us navigate and execute assertively. By upholding Holdex principles, we strive to create a positive and productive work environment that promotes innovation, accountability, and continuous growth. +Our Principles +DOs and DON'Ts +Availability Time +Our Tools +Guides + +✨ Our Principles +We align with the goals and execute them. Goals are the big picture we always keep in our heads. They are propelling our mission further. To achieve the goals, we decompose them into smaller problem statements. +We act as leaders and co-own the product. We define the work backlog ourselves, and no manager feeds us tasks. We take responsibility for solving the problems. +We are agile and deliver new increments daily. We decompose big problems into smaller ones, so we can complete them in not more than 4 hours. +We value our time. We have only one meeting with the team per week - that simple. We all work autonomously, communicate asynchronously, and collaborate ad hoc. Once a week, we demo what we’ve accomplished. +We wear many hats. We code, design, test, write articles, and hack things on Fridays because we love it. We’re here to build great products with like-minded people. +We figure things out ourselves. We learn terminology, read documentation, watch tutorials, or ask for information to learn from ourselves. + +DOs and DON'Ts + +✅ Do’s +❌ Don’t +Focus on what matters. Do the right thing. +Work on problems that don’t bring value to our goals. +Take ownership of the problem you are solving. +Run from responsibility. +If you are running away, tell others about it and explain your difficulties. + + +Put yourself in the user's shoes. Make sure you create things, not break them. Test your work well before claiming it’s complete. +Expect someone to test your work. +Before switching off, leave updates where you left off so others can pick it up. +Blackout and expect someone to chase you. + + + +🕑 Availability Time +Most of the team members are remote. However, we expect everyone to overlap work hours between 2-6 PM HKT daily. +🧰 Our Tools +When you start working with us, please ensure you have accounts and access to the following tools. + +Tool +Purpose +Github +Task management, source code storage, collaboration. Read our practice on how we use GitHub. +Vercel + + +Whimsical +Wireframing +Figma +Final designs +Calendar +Plan and book meetings +Google Chat +Discuss urgent or private matters. + + + +📖 Guides +💥How to Create Engaging Marketing Content +🤩How we compensate and help people grow at Holdex + +#principles #holdex + + From 2f2977834c9e12d1f66135ea8755b79516b1c05f Mon Sep 17 00:00:00 2001 From: Vadim Date: Wed, 16 Apr 2025 11:08:13 +0800 Subject: [PATCH 2/6] chore: simplify the copy Signed-off-by: Vadim --- .github/DONTS.md | 89 ++++++++++++++---------------------------------- 1 file changed, 25 insertions(+), 64 deletions(-) diff --git a/.github/DONTS.md b/.github/DONTS.md index bd57ce7..ed690b6 100644 --- a/.github/DONTS.md +++ b/.github/DONTS.md @@ -1,64 +1,25 @@ -As part of our team, it's essential to align yourself with these principles. -Both values and principles serve as the foundation for approaching our responsibilities and interacting with each other. In uncertain moments, our principles help us navigate and execute assertively. By upholding Holdex principles, we strive to create a positive and productive work environment that promotes innovation, accountability, and continuous growth. -Our Principles -DOs and DON'Ts -Availability Time -Our Tools -Guides - -✨ Our Principles -We align with the goals and execute them. Goals are the big picture we always keep in our heads. They are propelling our mission further. To achieve the goals, we decompose them into smaller problem statements. -We act as leaders and co-own the product. We define the work backlog ourselves, and no manager feeds us tasks. We take responsibility for solving the problems. -We are agile and deliver new increments daily. We decompose big problems into smaller ones, so we can complete them in not more than 4 hours. -We value our time. We have only one meeting with the team per week - that simple. We all work autonomously, communicate asynchronously, and collaborate ad hoc. Once a week, we demo what we’ve accomplished. -We wear many hats. We code, design, test, write articles, and hack things on Fridays because we love it. We’re here to build great products with like-minded people. -We figure things out ourselves. We learn terminology, read documentation, watch tutorials, or ask for information to learn from ourselves. - -DOs and DON'Ts - -✅ Do’s -❌ Don’t -Focus on what matters. Do the right thing. -Work on problems that don’t bring value to our goals. -Take ownership of the problem you are solving. -Run from responsibility. -If you are running away, tell others about it and explain your difficulties. - - -Put yourself in the user's shoes. Make sure you create things, not break them. Test your work well before claiming it’s complete. -Expect someone to test your work. -Before switching off, leave updates where you left off so others can pick it up. -Blackout and expect someone to chase you. - - - -🕑 Availability Time -Most of the team members are remote. However, we expect everyone to overlap work hours between 2-6 PM HKT daily. -🧰 Our Tools -When you start working with us, please ensure you have accounts and access to the following tools. - -Tool -Purpose -Github -Task management, source code storage, collaboration. Read our practice on how we use GitHub. -Vercel - - -Whimsical -Wireframing -Figma -Final designs -Calendar -Plan and book meetings -Google Chat -Discuss urgent or private matters. - - - -📖 Guides -💥How to Create Engaging Marketing Content -🤩How we compensate and help people grow at Holdex - -#principles #holdex - - +# ✅ 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 51912013dcd3b8bb7053b82e0d119575333fb622 Mon Sep 17 00:00:00 2001 From: Vadim Date: Wed, 16 Apr 2025 11:09:36 +0800 Subject: [PATCH 3/6] docs: follow link from main README Signed-off-by: Vadim --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index efa6730..f155841 100644 --- a/README.md +++ b/README.md @@ -6,4 +6,5 @@ This is where your contribution journey starts. Make sure to align yourself with: - [Contributing Guidelines](./.github/CONTRIBUTING.md) +- [DOs & DON'T](.github/DONTS.md) - [Sick Leave Policy](./.github/LEAVE_POLICY.md) From e61b2c64686d5c3a1c28e176f8250880f422f6f3 Mon Sep 17 00:00:00 2001 From: Vadim Date: Wed, 16 Apr 2025 11:12:15 +0800 Subject: [PATCH 4/6] docs: follow link from CONTRIBUTING page Signed-off-by: Vadim --- .github/CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 9bb4707..74661b1 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -3,7 +3,7 @@ Thank you for your interest in contributing to our project! Your accepted contributions will be reflected in our repositories and related websites. -Please read our [Code of Conduct](./CODE_OF_CONDUCT.md) to keep our community approachable and respectable. +Please read our [Code of Conduct](./CODE_OF_CONDUCT.md) to keep our community approachable and respectful. Also, if you are a permanent contributor, read our [DOs and DON'Ts](.github/DONTS.md). ## Getting started From 59e975d0da9d253466ef9ffb4e02a48d8b8ca495 Mon Sep 17 00:00:00 2001 From: Vadim Date: Wed, 16 Apr 2025 11:12:57 +0800 Subject: [PATCH 5/6] chore: improve readability Signed-off-by: Vadim --- .github/CONTRIBUTING.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 74661b1..f586a76 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -3,7 +3,8 @@ Thank you for your interest in contributing to our project! Your accepted contributions will be reflected in our repositories and related websites. -Please read our [Code of Conduct](./CODE_OF_CONDUCT.md) to keep our community approachable and respectful. Also, if you are a permanent contributor, read our [DOs and DON'Ts](.github/DONTS.md). +Please read our [Code of Conduct](./CODE_OF_CONDUCT.md) to keep our community approachable and respectful. +Also, if you are a permanent contributor, read our [DOs and DON'Ts](.github/DONTS.md). ## Getting started From 63e1e70c8fc0afa8f293ae69354d1c27fd1dc33d Mon Sep 17 00:00:00 2001 From: Vadim Date: Wed, 16 Apr 2025 11:20:11 +0800 Subject: [PATCH 6/6] docs: subscribe for notifications Signed-off-by: Vadim --- README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/README.md b/README.md index f155841..534c051 100644 --- a/README.md +++ b/README.md @@ -8,3 +8,6 @@ Make sure to align yourself with: - [Contributing Guidelines](./.github/CONTRIBUTING.md) - [DOs & DON'T](.github/DONTS.md) - [Sick Leave Policy](./.github/LEAVE_POLICY.md) + +Subscribe to this repository's notifications, as we frequently push fixes and updates. You must be in sync with those updates. +