lambdaclass / lambdaclass/lambdaclass_hacking_learning_path

Why Erlang? section

Open
#18 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
481
Forks
66
PR merge metrics
No merged PRs in 30d

Description

Explain why we like the Erlang/Elixir/BEAM platform as well as when and why we choose to use it.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Use issue #18 as the brief and first locate the handbook section where this explanation belongs. Write about why the project likes the Erlang/Elixir/BEAM platform and when and why it chooses to use it; done means the section covers both points clearly.

Written by the indexing model from the issue text.

Assessment

Tech stack
elixir, erlang
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.