Skip to content

Commit 9779f1c

Browse files
committed
chore: update sidebar to include 'global-communities' and remove 'career-development-communities'; delete outdated documentation files
1 parent f5f9107 commit 9779f1c

File tree

10 files changed

+264
-27
lines changed

10 files changed

+264
-27
lines changed

docs/career-development-communities.md

Lines changed: 0 additions & 1 deletion
This file was deleted.

docs/ci-cd.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,3 @@
1-
---
2-
sidebar_position: 4
3-
---
4-
51
# CI/CD
62

73
You’ve merged your pull request, tests are green, and everything looks good locally. Time to relax and move on? Not quite. In modern development, merging code is just the start. Your changes now enter the CI/CD pipeline—a set of automated steps that move code from your machine to production. Teams expect more than clean code; they expect you to understand and take ownership of the full lifecycle. CI/CD isn’t just jargon—it’s the core engine of DevOps, enabling fast, reliable delivery through automation and best practices.

docs/git.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,3 @@
1-
---
2-
sidebar_position: 2
3-
---
4-
51
# Git
62

73
You've written some great code and saved the file. Maybe you even zipped the project folder and named it project-final-v2-really-final.zip as a backup. Your work is safe and you're ready to share it with the team, right? Not quite. That old habit of manually managing versions is a recipe for confusion and lost work in any professional team.

docs/global-communities.md

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
# Global Communities
2+
3+
Building a successful tech career is not just about your technical skills—it's about connecting with the right communities that can guide you, support you, and open doors to opportunities you might never find on your own. By joining global tech communities, you gain access to resources that can help you grow professionally, find international opportunities, and connect with others who share similar experiences and ambitions.
4+
5+
## Why it matters
6+
7+
The tech industry moves fast, and staying connected with the right communities can make a big difference in your career growth. These communities offer more than just networking—they help with mentorship, job opportunities, interview preparation, and insights into what companies are really looking for.
8+
9+
Here's why joining global tech communities helps your career:
10+
11+
- **Access to opportunities**: Many jobs are shared in communities before they appear on job websites.
12+
- **Real-world advice**: Get honest feedback from people who work at the companies you want to join.
13+
- **Interview preparation**: Practice with others and learn from their experiences.
14+
- **Career guidance**: Connect with professionals who can guide your career decisions.
15+
- **Industry knowledge**: Stay updated on trends, technologies, and what skills companies need.
16+
17+
## Career programs that help you grow
18+
19+
### [Imagine Foundation](https://www.joinimagine.com/)
20+
21+
Imagine Foundation helps software engineers, data scientists, and product managers find tech jobs in Europe and other countries. What makes Imagine special is their personal approach—they don't just give generic advice, but work with you individually to improve your chances of success.
22+
23+
**What they offer:**
24+
25+
- **360° feedback**: A detailed 15-page report showing your strengths and areas where you need to improve.
26+
- **Personal career coaching**: One-on-one sessions with volunteer coaches who understand European hiring.
27+
- **CV and LinkedIn help**: Professional feedback to make your profile better.
28+
- **Job recommendations**: Direct connections to their 200+ partner companies.
29+
- **Interview coaching**: Preparation for technical and behavioral interviews.
30+
31+
**Two programs available:**
32+
33+
- **Job Booster (Free)**: Digital training, feedback, and coaching to get you started.
34+
- **Fellowship (Pay when you get hired)**: Complete support until you land a job, including unlimited coaching and direct company connections.
35+
36+
Imagine has helped over 700 developers from around the world, including many from the Middle East, successfully get jobs at European tech companies.
37+
38+
### [Manara](https://manara.tech/)
39+
40+
Manara focuses on helping software engineers and data scientists across MENA (Middle East and North Africa) learn AI and Cloud computing skills while connecting them to global job opportunities. All their programs are completely free.
41+
42+
**What they offer:**
43+
44+
- **AI and Cloud training**: Courses taught by Silicon Valley experts and AWS-certified teachers.
45+
- **Community support**: Study groups, mentorship, and peer learning.
46+
- **Interview practice**: AI-powered interview prep and expert-led sessions.
47+
- **Career assessment**: Professional review of your skills and resume.
48+
- **Job placement support**: Connections to global companies looking for MENA talent.
49+
50+
**Popular learning paths:**
51+
52+
- AWS AI Practitioner.
53+
- AWS Intro to Cloud Computing.
54+
- AI Fundamentals (coming soon).
55+
56+
Manara has trained over 150,000 learners across MENA and helped many get positions at companies like Amazon, Google, Meta, and Microsoft.
57+
58+
## Reddit Career Communities
59+
60+
Reddit has some of the most active and helpful career discussion communities for developers. These communities are where people share real experiences, ask for advice, and support each other through career challenges.
61+
62+
**[r/cscareerquestions](https://reddit.com/r/cscareerquestions)** The largest career community for computer science professionals with over 900,000 members. This is where you'll find:
63+
64+
- Salary discussions and company reviews.
65+
- Interview experiences and preparation tips.
66+
- Career advice from junior to senior levels.
67+
- Resume reviews and feedback.
68+
- Industry trends and job market insights.
69+
70+
**[r/cscareerquestionsEU](https://reddit.com/r/cscareerquestionsEU)** Specifically focused on tech careers in Europe, this community is particularly valuable if you're interested in European opportunities. You'll find:
71+
72+
- European job market insights.
73+
- Visa and relocation advice.
74+
- Company-specific information for European tech firms.
75+
- Salary information for European markets.
76+
- Cultural tips for working in different European countries.
77+
78+
**How to use these communities effectively:**
79+
80+
- **Read the rules**: Each subreddit has specific rules for posting.
81+
- **Search first**: Your question might already be answered in previous posts.
82+
- **Be specific**: Generic questions get generic answers.
83+
- **Give context**: Share your background, location, and specific situation.
84+
- **Help others**: Answer questions in areas where you have experience.

docs/mentorship.md

Lines changed: 72 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,73 @@
1-
---
2-
sidebar_position: 5
3-
---
4-
51
# Mentorship
2+
3+
You have worked hard on tutorials, built your own projects, and maybe even got your first job as a developer. But sometimes you face problems that are very hard to solve by yourself. Maybe you are confused about how to make big decisions in your code, how to grow in your career, or what to learn next. Having someone with more experience to guide you can really help. In today's fast-changing tech world, having a mentor is not just useful—it can be the difference between growing as a developer or feeling stuck and alone.
4+
5+
## Why it matters
6+
7+
Growing as a software developer is not just about writing more code or learning new tools. It's about learning how to think like an experienced developer, making good decisions when things get difficult, and building the skills that really matter when you work with a team.
8+
9+
Here's why having a mentor helps you grow faster:
10+
11+
- **Learn from someone else's experience**: A mentor has already made mistakes and learned from situations you haven't seen yet. They can help you avoid common problems and see opportunities you might miss.
12+
- **Get a learning plan made for you**: Instead of following random tutorials, a mentor can look at your specific situation and guide you toward the skills that will help your career the most.
13+
- **Understand how things really work**: Mentors help you understand the gap between what you learn alone and how things actually work in real jobs. They help you understand not just "what" to do but "why" you should do it.
14+
- **Learn about career growth**: Technical skills are important, but they're not everything. A mentor can help you understand how teams work, how to communicate better, and how to find opportunities to grow.
15+
- **Build confidence**: Having someone believe in you and give you honest feedback helps you take on challenges you might otherwise avoid.
16+
17+
Simply put, mentorship gives you years of experience in focused advice that fits your specific needs.
18+
19+
## Where to find mentors
20+
21+
While there are many global platforms that connect developers with mentors worldwide, the Syrian tech community has built something special—dedicated initiatives created by Syrian developers who understand our unique challenges and opportunities. These platforms don't just offer mentorship; they provide a bridge between Syrian talent and the global tech ecosystem. What makes these initiatives unique is that they're built by Syrian developers who have navigated the same challenges you're facing, and they're completely free to use.
22+
23+
### [Mentory](https://mentory-sy.net/)
24+
25+
Created by Syrian developers to connect Syrian developers with experienced mentors around the world. The platform offers different types of mentorship including technical guidance, career advice, academic support, and startup mentoring. With over 169 expert mentors from 27 countries, you can find someone who understands both your technical needs and cultural context. The mentors are Syrian professionals working at major tech companies globally, bringing real-world experience from international markets while understanding the Syrian context.
26+
27+
### [ProHelpify (P8Y)](https://prohelpify.com/en)
28+
29+
Another Syrian-led initiative that offers free consultation sessions with software experts. Their mentors work at companies like Meta, Tradinos, and other major tech organizations, providing insights into both local and international opportunities. The platform covers everything from interview preparation to career planning, with a focus on helping Syrian developers transition into global tech roles.
30+
31+
## How to be a good mentee
32+
33+
Getting the most from mentorship is not just about finding someone to help you—it's about being someone who is worth helping. Good mentees make the relationship valuable for both people and get the most growth for themselves.
34+
35+
### Come Ready and Focused
36+
37+
Show respect for your mentor's time by making every conversation useful and productive. This means doing your homework before each conversation and coming with specific questions or problems.
38+
39+
- **Ask specific questions**: Instead of "What should I learn next?", ask "I'm working on a React project and having trouble with state management. Can you help me understand when to use Context vs Redux?"
40+
- **Share your work**: Bring code examples, project demos, or specific problems you're facing. Real examples lead to better advice.
41+
- **Set clear goals**: Work with your mentor to decide what you want to achieve in the next few months. This could be learning a technology, getting better at code reviews, or preparing for a senior developer role.
42+
43+
### Be Consistent and Reliable
44+
45+
Building a strong mentorship relationship needs consistency and follow-through. Treat your mentorship commitments as seriously as you would any work commitment.
46+
47+
- **Keep your commitments**: If you schedule regular check-ins, show up prepared and on time
48+
- **Do what your mentor suggests**: Actually try the suggestions your mentor gives you, and tell them how it went
49+
- **Communicate early**: If you can't make a meeting or need to change the schedule, tell them in advance
50+
51+
### Listen Well and Ask Follow-Up Questions
52+
53+
Mentorship conversations are most valuable when you really engage with the advice you get. Don't just collect advice—understand the thinking behind it.
54+
55+
- **Ask "why" questions**: Understanding the reasons behind recommendations helps you use similar thinking in new situations.
56+
- **Ask for clarification**: If something isn't clear, ask for examples or different explanations.
57+
- **Take notes**: Write down key insights and action items so you can look back at them later.
58+
59+
### Share Your Progress and Problems
60+
61+
Keep your mentor informed about your development, including both successes and struggles. This helps them give you better guidance and adjust their approach as needed.
62+
63+
- **Share your wins**: Tell them about accomplishments that came from their guidance
64+
- **Be honest about difficulties**: If you're struggling with something they recommended, explain what's not working
65+
- **Ask for changes**: If your goals or situation changes, work with your mentor to adjust your learning path
66+
67+
### Give Back When You Can
68+
69+
Mentorship doesn't have to be a one-way relationship. Look for ways to provide value back to your mentor and the broader community.
70+
71+
- **Share useful resources**: If you find articles, tools, or opportunities that might interest your mentor, share them.
72+
- **Offer your skills**: You might be able to help with a project, give feedback on something they're working on, or share insights from your unique perspective.
73+
- **Help others**: As you grow, look for opportunities to help other developers who are earlier in their journey.

docs/observability.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,3 @@
1-
---
2-
sidebar_position: 4
3-
---
4-
51
# Observability
62

73
In modern software development, you don’t just build an application and hope it runs smoothly. You need to understand its internal state and behavior from the outside, across the entire stack—from a user's tap on a mobile screen to the deepest database query. This is observability. It’s not just about watching for errors (that’s monitoring); it’s about being able to ask questions about your system to understand why things are happening, especially in complex, distributed environments.

docs/open-source.md

Lines changed: 107 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,108 @@
1+
# Open Source
12

2-
# Open Source
3+
Contributing to open source is one of the best ways to grow as a developer, build your reputation, and connect with developers around the world. Open source gives you a way to show your skills to international employers and build professional relationships across borders.
4+
5+
## Why it matters
6+
7+
Open source contributions are more than just free work—they are investments in your professional development and career growth. Today, employers care more about practical experience than just certificates. Your open source contributions work like a public portfolio of your skills, work habits, and ability to work with others.
8+
9+
Here's why open source contributions help your career grow faster:
10+
11+
- **Public portfolio**: Your contributions are visible to anyone, anywhere in the world, showing proof of your skills and consistency.
12+
- **Real-world experience**: Working on production code used by thousands of people teaches you things tutorials never will.
13+
- **Code review and feedback**: Experienced maintainers will review your code, giving you valuable feedback that helps you improve.
14+
- **Professional networking**: You'll work with developers from around the world, building relationships that can lead to job opportunities.
15+
- **Learn from big projects**: You'll see how large, complex projects are built and learn best practices from experienced teams.
16+
17+
## How to get started
18+
19+
### Start Small and Be Consistent
20+
21+
The biggest mistake new contributors make is trying to work on major features right away. Successful open source contributors start with small, easy contributions and build their reputation over time. Some great ways to get started include:
22+
23+
- Fixing typos in README files or documentation
24+
- Improving code comments or adding missing documentation
25+
- Reporting bugs you find while using the project
26+
- Suggesting improvements to user guides or examples
27+
28+
### Choose Projects Wisely
29+
30+
Not all open source projects are good for beginners. Look for projects that welcome new contributors and have clear contribution guidelines.
31+
32+
**Look for these signs of a welcoming project:**
33+
34+
- Clear README with setup instructions
35+
- Contribution guidelines (usually in a CONTRIBUTING.md file)
36+
- Issues labeled "good first issue" or "beginner-friendly"
37+
- Active maintainers who respond to issues and pull requests
38+
- Code of conduct that promotes respectful collaboration
39+
40+
**Start with tools and libraries you already use:**
41+
42+
The best place to start is with tools and libraries you already use in your work or personal projects. You understand the problems they solve and can spot areas for improvement.
43+
44+
- If you use React, contribute to React-related projects
45+
- If you work with Node.js, find Node.js libraries that need help
46+
- If you're learning a new framework, contribute to its ecosystem
47+
48+
**Use GitHub's discovery features:**
49+
50+
GitHub provides several ways to find projects that need help:
51+
52+
- **GitHub Explore**: Visit github.com/explore to see trending projects, filter by language and topics you're interested in
53+
- **Good First Issues**: Search for "good first issue" labels across GitHub using GitHub's search filters
54+
- **Up For Grabs**: Visit up-for-grabs.net for a curated list of beginner-friendly projects organized by programming language
55+
56+
**Consider Syrian and Arabic projects:**
57+
58+
Look for projects created by Syrian developers or Arabic-speaking communities for easier communication, local context understanding, and stronger networking within the Syrian tech community.
59+
60+
### Follow Project Standards
61+
62+
Every project has its own way of doing things. Successful contributors learn and follow these standards rather than using their own preferences.
63+
64+
**Before making your first contribution:**
65+
66+
- Read the project's README completely
67+
- Review existing pull requests to understand the style and process
68+
- Check if there are coding standards or style guides
69+
- Look at recent commits to understand the project's direction
70+
71+
**When submitting contributions:**
72+
73+
- Follow the project's commit message format
74+
- Write clear, descriptive pull request descriptions
75+
- Include tests if the project requires them
76+
- Be responsive to feedback and requests for changes
77+
78+
### Build Good Relationships
79+
80+
Open source is about community, not just code. Building relationships with maintainers and other contributors is just as important as the technical contributions.
81+
82+
**Engage respectfully, professionally, and communicate clearly:**
83+
84+
- Be patient when waiting for reviews—maintainers are often volunteers.
85+
- Ask questions when you don't understand something.
86+
- Offer help to other contributors when you can.
87+
- Participate in project discussions and decisions.
88+
- Write clear, simple issues and pull request descriptions.
89+
- Be specific about problems and proposed solutions.
90+
91+
## Resources
92+
93+
### English Resources
94+
95+
- **[🎥 How to Contribute to Open Source Projects – A Beginner's Guide](https://www.freecodecamp.org/news/how-to-contribute-to-open-source-projects-beginner-guide/)**
96+
- **[📚 GitHub's Guide to Open Source](https://opensource.guide/)**
97+
- **[🎥 Open Source Explained](https://youtu.be/PVD1LNDxOnc)**
98+
- **[📚 First Timers Only](https://www.firsttimersonly.com/)**
99+
- **[🔗 Good First Issues](https://goodfirstissues.com/)**
100+
- **[🔗 Up For Grabs](https://up-for-grabs.net/)**
101+
- **[📚 How to Write the Perfect Pull Request](https://github.blog/2015-01-21-how-to-write-the-perfect-pull-request/)**
102+
103+
### Arabic Resources
104+
105+
- **[🎥 مقدمة في Open Source والمساهمة في المشاريع المفتوحة](https://youtu.be/3HqN-YS8eso)**
106+
- **[🎥 كيف تساهم في المشاريع مفتوحة المصدر؟](https://youtu.be/GNKPKhme8eM)**
107+
- **[🎥 أهمية المشاريع مفتوحة المصدر للمطورين](https://youtu.be/YL-f8WSw7I8)**
108+
- **[📚 دليل المطور العربي للمساهمة في المشاريع مفتوحة المصدر](https://blog.itwadi.com/posts/open-source-contribution-guide/)**

docs/testing.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,3 @@
1-
---
2-
sidebar_position: 3
3-
---
4-
51
# Testing
62

73
You’ve implemented the feature and tested it manually. Now you’re ready to move on to the next task—right? Not quite. The old idea of a developer writing code and tossing it over to QA is outdated. In today’s agile environments, you're expected to be the first and most important line of defense for code quality. It’s no longer enough for your code to "just work on your machine." To grow as a developer, you need to treat testing as a core part of your workflow—not an afterthought. Here’s what modern teams typically expect from you when it comes to testing.

docs/web.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,3 @@
1-
---
2-
sidebar_position: 1
3-
---
4-
51
# Web
62

73
## Why it matters

0 commit comments

Comments
 (0)