Use :mortar_board: for code quality improvements
See original GitHub issueHello @carloscuesta 😎!
I’d like to suggest a new emoji:
- Emoji: 🎓
- Code:
:mortar_board:
- Description: Improve code quality
The issue is: None of the current emojis describes the change i want to see, where functionality was not changed (=remained the same) but the quality of the code was improved.
Example: Removed a hardcoded string from the code and put it into an helper class as constant or function.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:5
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Improve code quality with these 4 steps - New Relic
3. Build development-quality dashboards. Identify the technology that supports your development processes, such as source code repositories and ...
Read more >8 Practices to Ensure Better Code Quality | by Kasun Rajapakse
Here is a list of practices for improving code quality that will be useful for any software project. 1. Use Linter at IDE...
Read more >4 tips to improve code quality - Work Life by Atlassian
4 tips to improve code quality · 1. Embrace coding conventions · 2. Use a code linter · 3. Adopt continuous integration ·...
Read more >What Is Code Quality? Overview + How to Improve ... - Perforce
Code quality metrics defines code that is good (high quality) — and code that is bad (low quality). Learn how to measure code...
Read more >Tools to Improve Code Quality - DEV Community
Other popular tools teams use to track maintenance issues are: Project management tools, like Jira; List tracking apps, like Trello; Excel ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Saw that @WaKeMaTTa but Heavy refactoring seems not to be appropriate in this case.
Looks good changing “heavy refactoring” to “Refactoring code” then 👍 @avoelkl