Developer Playground is home to many subprojects. Subprojects are essentially test beds for programming languages and contain what is widely deemed as best practice to achieve good coding.
New subprojects can be added by following this process:
- Decide your programming language name, one word is best
- Create your icon using an example like this - modify the URL to meet need
- Contact an admin giving details of the language name and icon URL
Please note that Developer Playground has branch-rules in place to protect content and users. An administrator is needed to bypass settings to create a new language branch.
If you are interested in helping to administer, please do reach out.
Getting involved with your language of choice is a great idea; you can showcase your knowledge as an early adopter and set the bar for developers of all levels to start experimenting. It is heavily encouraged to 'weigh in' on pull requests to offer advice and begin discussions. You never know, you might ignite a spark in the mind of a young programmer.
Collaboration necessitates recognising that contributors may possess varying levels of expertise and comprehension. It's crucial to embrace the diverse perspectives, experiences, and skills our colleagues bring to the table, as this collective effort can facilitate learning and illuminate previously obscure areas.
We should actively promote even the most minor steps toward positive progress and stand ready to support our colleagues during difficult times.
Failure and success are two contrasting outcomes or states that often play a significant role in shaping our lives and experiences. Here's a breakdown of each concept:
Learning opportunity: Failure is often considered a valuable learning experience. It provides insights into what didn't work and can lead to personal growth and development.
Emotional impact: Failure can be emotionally challenging. It may lead to feelings of disappointment, frustration, or even sadness. However, it can also build resilience and the ability to cope with setbacks.
Motivation: Failure can serve as motivation to improve and try again. Many successful individuals have faced multiple failures before achieving their goals.
Risk-taking: Failure is an inherent part of taking risks. Without the possibility of failure, there is often limited room for innovation and growth.
Recognition: Success is often accompanied by recognition and praise from others, which can boost self-esteem and confidence.
Emotional impact: Success can bring feelings of happiness, satisfaction, and pride. It can also provide a sense of accomplishment and validation.
Motivation: Success can serve as motivation to continue striving for excellence and setting higher goals.
It's important to note that failure and success are not always mutually exclusive. Many successful individuals have experienced failure at various points in their lives, and failure can be a stepping stone to eventual success. Additionally, what is considered a failure or success can be highly subjective and dependent on one's perspective and goals. Ultimately, both failure and success are part of the journey of life, and how we perceive and respond to them can shape our future experiences.
Each language branch contained in this project has been orphaned. An orphan branch is a term commonly used in version control systems like Git. It refers to a branch with no parent or history connection to other branches in the repository. In other words, an orphan branch is created independently and does not share a common commit history with any other branch. This branch starts fresh with no commits, and any changes made to it are isolated from the rest of the project's history until the branch is merged or connected to another branch.
An orphan branch is created using the git checkout --orphan command followed by the branch name. For example:
git checkout --orphan <branch_name>Orphan branches are locked under branch rules and will need pull requests, in the usual way, to add features.
The community creates conventions, so please do offer your thoughts in Discussions
The headings below offer some support to help us with some housekeeping.
This repository houses multiple languages, which can make viewing branches a little tricky. Let us subscribe to the following convention:
- Begin branch names with the language your code is intended
- Follow with a dash
-and the wordapply - Complete with a forward slash
/ - Next, write your branch name as you would normally
You can model it like so:
ruby-apply/my-awesome-new-ruby-branch