Don't repeat yourself!
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 17
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
DRY (Don't Repeat Yourself) principal from The Pragmatic Programmer
It's good practice to aim for DRY code as opposed to WET code! ("Write everything twice", "We enjoy typing", "Waste everyone's time")
This is a good mentality to keep in mind whenever you're writing code, documentation, working on data/ database design etc., and can be a good thing to remind yourself to prevent a short-term mindset. Taking the time to take a step-back, and plan the architecture of the project pays off not only for you using the code right now, but for anyone who wants to use it in the future!
See also #83 and #84
(Repetitive shapes could be a good sign that you should refactor, and dry your code out!😉)
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
No files, tests, or entry points are identified. Read this issue alongside related issues #83 and #84, then establish a concrete duplication to address and an agreed scope before starting; completion cannot be determined from the current description.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100