Skip to content

docs: update link to lambda ethos #173

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pablodeymo merged 1 commit into from
Mar 2, 2026
Merged

docs: update link to lambda ethos #173

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Before diving in, we recommend reading [our introductory blog post](https://blog

## Philosophy

ethlambda follows the [LambdaClass work ethos](https://blog.lambdaclass.com/): simplicity is not the opposite of capability, but its foundation. Every contribution should uphold this.
ethlambda follows the [LambdaClass work ethos](https://blog.lambdaclass.com/lambdas-engineering-philosophy/): simplicity is not the opposite of capability, but its foundation. Every contribution should uphold this.

- **Lines of code matter.** We track LoC. ethlambda targets staying under a strict limit. If you can remove lines without losing clarity, do it.
- **Vertical integration.** Flat structure, self-explanatory crates. If you can't explain a module in one sentence, it's doing too much.
Expand Down