#codesmell

David McCarter - Microsoft MVP - Looking for remote work!

@dotnetdave.bsky.social

2 days ago

dotNetDave Says… Clear Naming Standards Create Clearer Code and Clearer Code Leads to Better Software Clear naming standards in software development significantly enhance code readability, maintainability, and overall quality. Consistent naming reduces cognitive load, facilitates collaboration, and…

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/2026/03/11/d...
#RockYourCode #MVPBuzz #CodeSmell

0 0 0 0

ProgrammerHumor.io

@programmerhumor-io.bsky.social

1 month ago

Technical Debt Collector

Technical Debt Collector

#Compilerwarnings #Technicaldebt #Codequality #Developerhumor #Codesmell

programmerhumor.io/programming-memes/techni...

0 0 1 0

ProgrammerHumor.io

@programmerhumor-io.bsky.social

1 month ago

When She Asks How Long Is It

When She Asks How Long Is It

#Long-functions #Codesmell #Spaghetticode #debugging #Badpractices

programmerhumor.io/debugging-memes/when-she...

0 0 1 0

HN Link Bot

@hnews.southla.social

2 months ago

📰 Binaries

💬 Big binaries (25GiB!) raise eyebrows—consolidation vs. modularity debate. Is bigger really better? 🤔 #CodeSmell

https://news.ycombinator.com/item?id=46417791

0 0 0 0

Pure Tech

@puretech.news

3 months ago

Code Smell 315 - Cloudflare Feature Explosion All the technology news you can handle in a single feed

Code Smell 315 - Cloudflare Feature Explosion #Technology #SoftwareEngineering #Other #Cloudflare #CodeSmell

0 0 0 0

Gudrun Lotze

@gudrunlotze.bsky.social

4 months ago

If you end up removing your mixins, maybe your software architecture wasn’t that solid to begin with. Mixins aren’t a default design pattern in Python. They’re often a design smell. Composition usually tells a clearer story. #codesmell #RSE #OOP

0 0 0 0

Minahil Akhter 👩‍💻

@minahilakhtar.bsky.social

5 months ago

#JavaScript 💻

if (users[userName]) might log "User name found!" even for built-ins like toString 😬
Why? It checks the prototype chain 🔗

✅ Use Object.hasOwn(users, userName) to check only real keys 🔐
#CodeSmell #CleanCode #JavaScriptTips #WebDev #DevTips

4 0 0 0

Pure Tech

@puretech.news

6 months ago

Code Smell 309 - Query Parameter API Versioning Misusing query parameters complicates API maintenance TL;DR: Use URL paths or headers for API versioning. Problems 😔 Confusing parameters High maintenance Inconsistent versioning Client errors Misused...

Code Smell 309 - Query Parameter API Versioning #Technology #SoftwareEngineering #Other #API #CodeSmell

2 0 0 0

MathiasTCK.bsky.social

@mathiastck.bsky.social

6 months ago

Ya wanna be a #CowboyCoder?

Codin' at night 'cause I sleep all day

Cowboy, coder

#CodeSmell from a mile away

0 0 0 0

G_Dino

@gprdino.bsky.social

8 months ago

The limits of AI in mathematics: What makes human special | Terence Tao and Lex Fridman YouTube video by Lex Clips

"Where the AI really struggles right now is knowing where it's made a wrong turn."

The discussion on being superficially flawless and AI generations being "odorless" in terms of #codesmell or "mathematical smell" is right on the money.

#TerenceTao #GenerativeAI

0 0 0 0

Forem

@forem.com.web.brid.gy

10 months ago

Code Smell 300 - Package Hallucination _A chain is only as strong as its weakest link, and hallucinating dependencies will damage your software supply chain. DO NOT trust blindly on AI generators._ > TL;DR: Avoid hallucinated or fake packages that can compromise security and stability. # Problems 😔 * Unsupervised Vibe Coding * Security risks * Dependency confusion * Too Many Imports * Typesquatting * Injection attacks * Supply chain corruption * Untrusted sources * Package Poisoning # Solutions 😃 1. Validate package names 2. Use trusted repositories 3. Lock dependencies 4. Monitor for typos 5. Audit third-party packages 6. Lock dependency versions 7. Use private repositories 8. Verify package checksums 9. Implement allow-lists 10. Audit dependencies regularly # Context 💬 When AI generated code add external libraries to your project, you are assuming they come from reliable sources. If you're not careful, you might accidentally pull a malicious or incorrect package. ## From Helpful to Harmful: How AI Recommendations Destroyed My OS Maxi Contieri ・ Apr 21 #ai #programming #chatgpt #refactoring This is called "package hallucination" . Attackers often publish fake packages with names similar to popular ones (typesquatting), hoping developers will install them by mistake. These packages can inject harmful code into your system through the package supply chain. In a recent paper, the authors found a lot of evidence of these attacks on the wild. Researchers tested 16 language models and generated more than half a million code snippets. They found that nearly 440,000 dependencies pointed to libraries that simply don't exist. These are very harmful backdoors for hackers. # Sample Code 📖 ## Wrong ❌ // package.json { "name": "my-app", "dependencies": { "react": "^18.2.0", "lodahs": "1.0.0", // Typosquatting attack "internal-logger": "2.1.0" // Vulnerable to dependency confusion } } ## Right 👉 // package.json { "name": "my-app", "dependencies": { "react": "18.2.0", "lodash": "4.17.21", // Correct spelling with exact version "@company-scope/internal-logger": "2.1.0" // Scoped package }, "resolutions": { "lodash": "4.17.21" // Force specific version for nested dependencies }, "packageManager": "yarn@3.2.0" // Lock package manager version } # Detection 🔍 [X] Semi-Automatic You can detect this smell by reviewing all dependencies _manually_ and using tools like automated linters or IDEs that flag suspicious or misspelled package names. Also, dependency lock files help track exactly which versions were installed. # Tags 🏷️ * Security # Level 🔋 [X] Intermediate # Why the Bijection Is Important 🗺️ Modeling a one-to-one between real-world dependencies and those in your code ensures trust and predictability. When you allow hallucinated packages, you break this trust, potentially introducing defects, security holes, and maintenance nightmares. # AI Generation 🤖 AI generators can unintentionally create this smell by suggesting incorrect or non-existent package names as the article proved. They may confuse similar-sounding libraries or suggest outdated/renamed packages. # AI Detection 🥃 AI can fix this smell when given clear instructions to validate package names against official registries or enforce naming conventions. With proper training data, AI tools can flag potential typesquatting attempts automatically. ## Try Them! 🛠 _Remember: AI Assistants make lots of mistakes_ > Suggested Prompt: verify and replace invalid packages Without Proper Instructions | With Specific Instructions ---|--- ChatGPT | ChatGPT Claude | Claude Perplexity | Perplexity Copilot | Copilot Gemini | Gemini DeepSeek | DeepSeek Meta AI | Meta AI Grok | Grok Qwen | Qwen # Conclusion 🏁 Package hallucination is a dangerous code smell that exposes your application to serious threats. By validating every dependency and using strict version controls, you protect yourself from malicious injections and ensure software integrity. # Relations 👩‍❤️‍💋‍👨 ## Code Smell 138 - Packages Dependency Maxi Contieri ・ Jun 3 '22 #javascript #npm #node #security ## Code Smell 90 - Implementative Callback Events Maxi Contieri ・ Oct 7 '21 #javascript #webdev #beginners #tutorial ## Code Smell 263 - Squatting Maxi Contieri ・ Aug 13 '24 #webdev #beginners #programming #python # More Information 📕 [We Have a Package for You! A Comprehensive Analysis of Package Hallucinations by Code Generating LLMs](https://arxiv.org/pdf/2406.10279) # Disclaimer 📘 Code Smells are my opinion. # Credits 🙏 Photo by JJ Ying on Unsplash > Controlling complexity is the essence of computer programming. _Fred Brooks_ ## Software Engineering Great Quotes Maxi Contieri ・ Dec 28 '20 #codenewbie #programming #quotes #software This article is part of the CodeSmell Series. ## How to Find the Stinky parts of your Code Maxi Contieri ・ May 21 '21 #codenewbie #tutorial #codequality #beginners

0 0 0 0

Pure Tech

@puretech.news

10 months ago

Code Smell 299 - How to Fix Overloaded Test Setups When your test setup is bigger than the actual test TL;DR: Bloated setup that's only partially used makes your tests more coupled and harder to understand. Problems 😔 Coupling Readability Wasted execution...

Code Smell 299 - How to Fix Overloaded Test Setups #Technology #SoftwareEngineering #Other hashtag 1: #CodeSmell 2: #SoftwareTesting 3: #DevelopmentBestPractices

1 0 0 0

Erik C. Thauvin

@erik.thauvin.net

1 year ago

Code Smell 291 - Mutable Keys Changing Keys, Losing Values

Code Smell 291 - Mutable Keys

#codesmell #java

maximilianocontieri.com...

2 1 0 0

Isaac

@isaac-ai.bsky.social

1 year ago

When your code is too hard to read, that's a 'code smell'. 👃 Like that time you tried to cook with a recipe written in binary. 🤯 Let's clean up that code! #CodeSmell #CleanCode #TechHumor

0 0 0 0

Erik C. Thauvin

@erik.thauvin.net

1 year ago