If your code needs a walkthrough every time someone opens a file… naming is the problem. Clear naming standards create clearer code—and clearer code leads to better software. dotNetDave breaks it down 👇 dotnettips.wordpress.com/202… #RockYourCode #MVPBuzz #CodeSmell

1. Eu li a doc 2. Até onde eu sei não coloquei nome de ninguém, e eu posso ter visto essa PR em qualquer lugar ou ter falado isso por puro meme kk 3. Gerar chaves dinamicamente direto no componente é um codesmell e está escrito na doc, voce perde o contexto e é mais lento, acho que ninguém quer deixar a aplicação mais lenta propositalmente

Damn you os._exit! #python #codesmell

¿Patrones de diseño? Ni todo ni nada: bien usados, salvan tu código; mal usados, lo hacen incomprensible. Te cuento dónde está el truco y ejemplos claros. Mira esto 👉 youtu.be/_5X-_kuklvU #CodeSmell #BestPractices

🔵 𝐓𝐢𝐫𝐞𝐝 𝐨𝐟 𝐁𝐚𝐝 𝐂𝐨𝐝𝐞? 𝐀𝐯𝐨𝐢𝐝 𝐓𝐡𝐞𝐬𝐞 𝟕 𝐂𝐨𝐦𝐦𝐨𝐧 𝐌𝐢𝐬𝐭𝐚𝐤𝐞𝐬 Bad code doesn’t start with bad developers. It starts with small, careless decisions that accumulate over time… Here are 7 real mistakes I’ve seen (and fixed) in production environments, and they may be hiding in your code too: 𝟏 – 𝐌𝐚𝐠𝐢𝐜 𝐬𝐭𝐫𝐢𝐧𝐠𝐬 𝐚𝐧𝐝 𝐧𝐮𝐦𝐛𝐞𝐫𝐬 Hardcoded values make your code brittle and unreadable. Extract them now! 𝟐 – 𝐔𝐬𝐢𝐧𝐠 𝐂𝐨𝐦𝐦𝐞𝐧𝐭𝐬 𝐚𝐧𝐝 𝐑𝐞𝐠𝐢𝐨𝐧𝐬 If you need comments to explain your code, maybe it’s your code that needs fixing. 𝟑 – 𝐄𝐦𝐩𝐭𝐲 𝐂𝐚𝐭𝐜𝐡 𝐛𝐥𝐨𝐜𝐤𝐬 Ignoring errors isn’t error handling, it’s error hiding. 𝟒 – 𝐔𝐬𝐢𝐧𝐠 𝐌𝐚𝐩𝐩𝐢𝐧𝐠 𝐋𝐢𝐛𝐫𝐚𝐫𝐢𝐞𝐬 Mapping libraries sound great in theory: write less code, map objects automatically, and move faster. In practice, they often introduce more confusion than clarity. 𝟓 – 𝐍𝐨𝐭 𝐯𝐚𝐥𝐢𝐝𝐚𝐭𝐢𝐧𝐠 𝐲𝐨𝐮𝐫 𝐜𝐨𝐝𝐞 Never trust external input. Ever. Validation is non-negotiable. 𝟔 – 𝐂𝐨𝐧𝐟𝐮𝐬𝐢𝐧𝐠 𝐦𝐞𝐭𝐡𝐨𝐝 𝐚𝐧𝐝 𝐯𝐚𝐫𝐢𝐚𝐛𝐥𝐞 𝐧𝐚𝐦𝐞𝐬 Name things clearly. Future you (and your team) will thank you. 𝟕 – 𝐔𝐬𝐢𝐧𝐠 𝐞𝐱𝐜𝐞𝐩𝐭𝐢𝐨𝐧𝐬 𝐟𝐨𝐫 𝐞𝐱𝐩𝐞𝐜𝐭𝐞𝐝 𝐜𝐚𝐬𝐞𝐬 If a user sends bad input, or a record isn’t found, that’s not exceptional. That’s expected. These may look innocent, but they slowly kill maintainability, testability, and performance. I broke each one down on my blog with examples and solutions that you can start applying today. 𝐋𝐢𝐧𝐤 𝐢𝐬 𝐢𝐧 𝐭𝐡𝐞 𝐜𝐨𝐦𝐦𝐞𝐧𝐭𝐬! 💬 Which of these mistakes have you seen (or made)? ❤️ Like if you’ve fixed any of these in the past! 🔁 Repost to help others clean up their codebase. #DotNet #CSharp #CleanCode #CodeQuality #SoftwareEngineering #DeveloperTips #Refactoring #BackendDevelopment #AspNetCore #CodingMistakes #ProgrammingTips #CodeSmell #SoftwareCraftsmanship

🐛「バグの温床はここだ！」 こんにちは、#阿久梨絵 です！ 🧠Code Smellを見抜く視点が、健全なコードの第一歩。 🔍設計の歪みは、静かにバグを育てる。 #プログラミング #CodeSmell #リファクタリング 🧑‍💻📐💥 aqlier.com/2025/07/22/code_s…

lmao u created the ultimate codesmell u didn’t even need to show the copied comments

Java Tip 💡: Avoid long parameter lists, use objects or builders instead. #Java #CodeSmell

📢 Our article “When Code Smells Meet ML: On the Lifecycle of ML-specific Code Smells in ML-enabled Systems” has been accepted in the EMSE Journal! 🔍 #SE4AI #CodeSmell #TechnicalDebt #EmpiricalSE 📄 Paper: gilbertrec.github.io/persona… 💻 Tool: github.com/giammariagiordano…

I mean, sure what you’re proposing makes sense. But I’ve been building @RepoPrompt for months, using it heavily to improve it. I don’t run into context issues very often. If I do, it’s usually a self inflicted wound. Codemaps do a great job at bridging understanding of files without needing their full context. More files is best, but you can get work with very large files without issue. I use diff editing to update them with great success. 100k tokens for a file is a codesmell even without ai.

Understandable and I hold same views to a good extent. UI packages when you have the time feel like a codesmell, unfortunately for me, I don't have the time. I implemented it once myself in 2021 iirc, and found it faster with the package especially for different border styles

There is no world where AMC and GameStop should be said in the same sentence, unless it's talking about polar opposites. #codeSmell

The usual argument against using a flag argument is that it results in messier function code, couples different concerns, and is harder to understand and maintain. bit.ly/3VGnI6o #CSharp #CodeSmell

【Qiita】3年前にすごい人 [ リファクタリング バグ 組み込み 品質 codesmell ]に関する記事を書いた @kazuo_reve さん : qiita.com/kazuo_reve/items/8…

this is what codesmell smells light right here ☝️

Po pior que eu curto seus frames amigo e dentro deles não vejo problema nenhum de usa-los. Mas o optimal pra mim seria importar por escopo mesmo, dentro do contexto do Node claro. A real é que o que me deixa puto com DI é quando fazem overDI que é um codesmell, mas não vejo problemas nos outros casos

Ovo je boljka od koje sam decenijama bolovao. U moju odbranu, na kraju bi se ispostavilo da ipak treba. Sreća. Speculative Generality - Sometimes code is created "just in case" to support anticipated future features that never get implemented refactoring.guru/smells/spec… #codesmell

0 useEffect: ok 1 useEffect: tolerável em algumas situações 2 useEffect: codesmell 3 useEffect: demissão sem justa causa 4 useEffect: demissão com justa causa 5 useEffect: demissão com justa causa sair escoltado da empresa 6 useEffect: demissão nome sujo no mercado d trabalho

Are Boolean Flags on Methods a Code Smell? bit.ly/3Un4MdR #CSharp #CodeSmell

codesmell aber eigentlich emitted dieser von meinen ungewaschenen hoden