Code Smells sind Hinweise darauf, dass im Code etwas nicht sauber ist - etwas schlecht riecht. Es geht nicht um Syntaxfehler oder Bugs, so...

magicmarcy.de/code-smells-was-riecht-d...

#CodeSmells #Methoden #Logik #Parameter #MagicStrings #MagicNumbers #Programming #Awareness

Kissy is reviewing my pull request...

What faces do you make when you look over poorly written code?

#dev #devcat #programmer #codereview #codesmells #codercat #badcode

To support future PhD candidates joining thesis contests, I prepared a short pitch video with the presentation I gave in the final stages of these competitions.

It has 🇧🇷 audio and manually created 🇧🇷🇬🇧 subtitles — ideal for both academics and practitioners.

#CodeSmells #Refactoring #SoftwareQuality

measured improvement in server performance

wiki.c2.com/?CodeSmell

#codesmells #rewriting #coding #programming #patternlanguage #wardswiki #c2wiki

My database schema has more red flags than a PHP conference. Needs SQL fixes, therapy, and possibly an intern to blame. #Database #PHP #CodeSmells

Understanding Code Smell ## What is Code Smell? Code smell refers to any symptom in the source code that may indicate a deeper problem. While it may not immediately cause bugs, it points to weaknesses in the code's structure or design that could make the system harder to maintain, read, and extend in the future. ## Why is Understanding Code Smell Importan? Uderstanding code smells is essential because it helps us: * Maintain code quality. * Facilitate code maintenance and future development. * Reduce the chance of introducing bugs. * Avoid problems caused by poor design choices. * Build a professional portofolio as backend developer. Here are some of the most common types of code smell, along with brief explanations and simple examples. ### 🔹 Duplicated Code This happens when the same code appears in multiple places. it makes maintenance harder because if something change, you have to update it everywhere. Example: public int add(int a, int b) { return a + b; } public int addThree(int a, int b, int c) { return a + b + c; } Solution: Combine the duplicated logic into one flexible method. ### 🔹 Long Method A method that's too long and does too many things is hard to understand and test. Example: public void processOrder() { validateOrder(); calculateDiscount(); applyTax(); generateInvoice(); sendNotification(); } Solution: Break it into smaller methods, each with a single, clear responsibility. ### 🔹 Feature Envy This occurs when a method relies too much on another class's data or behavior. Example: public String getCustomerInfo(Customer customer) { return customer.getName() + ", " + customer.getAddress(); } Solution: Move this logic to the relevant class (in this case, `Customer`). ### 🔹 Large Class A class that has too many responsibilities can become hard to manage. Example: public class OrderManager { void createOrder() {} void cancelOrder() {} void calculateTotal() {} void sendNotification() {} } Solution: Split it into smaller classes, each handling one responsibility. ### 🔹 Primitive Obsession Using primitive types (like `String` or `int`) instead of creating classes to represent complex concepts. Example: public class User { private String phoneNumber; private String email; } Solution: Create a `ContactInfo` class to encapsulate contact details. ### 🔹 Long Parameter List A method that takes too many parameters can be confusing and hard to work with. It's easy to forget the correct order of the parameters, and it clutters the method signature. Example: public void createUser(String name, String email, String phone, String address, String city, String postalCode) { // logic } Solution: Group related parameters into a class or object, such as a `UserProfile` or `ContactInfo`. #### Consolusion Code smells are not bugs, but they signal that the code could be improved. By recognizing and addressing these semlls, you can write cleaner, more maintainable, and professional code.

0 Errors. 0 Warnings. Something’s Definitely Wrong⚠️
When the silence is just... too quiet.
Trust your instincts: techgeeksapparel.com/0-erro...
#CodeSmells #DebugMode #DevHumor

New version of Vogen with improved handling for numbers in Dapper and improved System.Text.Json deserialisation.

I've done nothing for this release; it's been done entirely by no fewer than 5 fantastic contributors! Thank you!

github.com/SteveDunn/Vo...

#dotnet #ddd #codesmells #nearly1000stars

Refactoring code: like tidying up a messy room 🧹. You know it's good when your future self sends you flowers 💐
But sometimes it's like moving furniture during an earthquake. 🥴
Fix: 1. Small steps. 2. Tests! 3. Version control. #Refactor #CodeSmells #Tech

If something seems off in the code, it could be a familiar code smell. We share some common code smells to be aware of here:

https://bit.ly/4c7hLpg

#DevIQ #CodeSmells

Rule 3: No Code Comments 🚫💬
If your code needs comments, rewrite it! Make it self-explanatory. Comments are for poets, not coders. (Agree or disagree with this one? I'd love to hear your thoughts on this topic.)
#DevTips #CodeSmells

🎥 Here's the video recording of our meetup on code smells folks! 🚀

Check it out here: www.youtube.com/watch?v=q09w...

Thanks again, @bischoffdev.bsky.social ! 🙌🎉

#CodeSmells #ContinuousTesting