practicalli / practicalli/clojure
Naming functions in clojure, a guide by stuart sierra
Open
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 117
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
https://stuartsierra.com/2016/01/09/how-to-name-clojure-functions
Related general concepts on abstractions
http://wiki.c2.com/?RavioliCode
https://georgik.rocks/spaghetti-lasagna-and-raviolli-code/
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the linked Stuart Sierra article and the two abstraction references first. The issue does not name a repository file, entry point, test, documentation location, or acceptance criteria, so confirm the intended change and definition of done with maintainers before starting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100