Cryptic Code is Bad Code TL;DR: Avoid obfuscated functions in your code. This article is based on a real social hacking event disguised as a job interview Problems Hidden vulnerabilities
Readability
Testability
Trust issues
Bad Naming Solutions Use clear names
Avoid obfuscation
Explain intent clearly
Review shared code
Don't trust code from unreliable sources
Avoid modification since it is a sign of Premature Optimization Context When you write functions with cryptic or obfuscated names, you make your code unreadable and untrustworthy. This pattern often hides malicious intent or makes debugging and collaboration unnecessarily hard. Cryptic code also frustrates team members and future maintainers, increasing technical debt and security risks. Remember, hacking has a strong social component compared to what you see in Hollywood movies. Sample Code Wrong function _0xaexad(_0x12bfc3, _0x43a1e9) {
  return _0x12bfc3 ^ _0x43a1e9;
}

const result = _0xaexad(0x1a, 0x2f);
console.log(result); Right function xorOperation(orValue1, orValue2) {
  return orValue1 ^ orValue2;
}

const result = xorOperation(26, 47);
console.log(result); Detection [x]Automatic You can detect this smell by scanning your codebase for meaningless or obfuscated function names. Use linters or code analysis tools to flag short, cryptic, or randomly named functions. Manual code reviews can also help identify suspicious patterns. Tags Security Level [x]Intermediate Why the Bijection Is Important Readable and meaningful names create a one-to-one correspondence between the real-world concept and your code. Breaking this connection makes your program confusing and error-prone. AI Generation AI generators sometimes produce cryptic function names, especially when they optimize for brevity or imitate obfuscated patterns. AI Detection AI tools can detect and fix this smell when you ask them to refactor unclear function names or enforce coding standards. They can analyze your entire codebase and suggest meaningful replacements for obfuscated names. Try Them!
Remember: AI Assistants make lots of mistakes Without Proper Instructions

With Specific Instructions



ChatGPT

ChatGPT



Claude

Claude



Perplexity

Perplexity



Copilot

Copilot



Gemini

Gemini Conclusion Avoid obfuscating your function names. Write code that communicates your intent. When you prioritize readability, you make your software easier to understand, debug, and maintain. Cryptic code might look clever, but it adds unnecessary complexity. Related Reading https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xxviii https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xliii https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-ii-o96s3wl4 https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-iv-7sc3w8n More Info https://www.linkedin.com/posts/franco-aguilera-2583685a_the-code-challenge-scam-they-tried-to-hack-activity-7270114822950703107-K3DW/?embedable=true Disclaimer: Code Smells are my opinion. Credits: Photo by Nikita Pavlov on Unsplash The strength of a cryptographic system depends entirely on the strength of its weakest component.
- Bruce Schneier https://hackernoon.com/400-thought-provoking-software-engineering-quotes?embedable=true This article is part of the CodeSmell Series. https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-i-xqz3evd?embedable=true Cryptic Code is Bad Code TL;DR: Avoid obfuscated functions in your code. TL;DR: Avoid obfuscated functions in your code. This article is based on a real social hacking event disguised as a job interview real social hacking event disguised as a job interview Problems Hidden vulnerabilities Readability Testability Trust issues Bad Naming Hidden vulnerabilities Readability Testability Trust issues Bad Naming Solutions Use clear names Avoid obfuscation Explain intent clearly Review shared code Don't trust code from unreliable sources Avoid modification since it is a sign of Premature Optimization Use clear names Avoid obfuscation Explain intent clearly Review shared code Don't trust code from unreliable sources Avoid modification since it is a sign of Premature Optimization Premature Optimization Context When you write functions with cryptic or obfuscated names, you make your code unreadable and untrustworthy. This pattern often hides malicious intent or makes debugging and collaboration unnecessarily hard. Cryptic code also frustrates team members and future maintainers, increasing technical debt and security risks. Remember, hacking has a strong social component compared to what you see in Hollywood movies. Sample Code Wrong function _0xaexad(_0x12bfc3, _0x43a1e9) {
  return _0x12bfc3 ^ _0x43a1e9;
}

const result = _0xaexad(0x1a, 0x2f);
console.log(result); function _0xaexad(_0x12bfc3, _0x43a1e9) {
  return _0x12bfc3 ^ _0x43a1e9;
}

const result = _0xaexad(0x1a, 0x2f);
console.log(result); Right function xorOperation(orValue1, orValue2) {
  return orValue1 ^ orValue2;
}

const result = xorOperation(26, 47);
console.log(result); function xorOperation(orValue1, orValue2) {
  return orValue1 ^ orValue2;
}

const result = xorOperation(26, 47);
console.log(result); Detection [x]Automatic [x] Automatic [x] You can detect this smell by scanning your codebase for meaningless or obfuscated function names. Use linters or code analysis tools to flag short, cryptic, or randomly named functions. Manual code reviews can also help identify suspicious patterns. Tags Security Security Level [x]Intermediate [x] Intermediate [x] Why the Bijection Is Important Readable and meaningful names create a one-to-one correspondence between the real-world concept and your code. one-to-one Breaking this connection makes your program confusing and error-prone. AI Generation AI generators sometimes produce cryptic function names, especially when they optimize for brevity or imitate obfuscated patterns. AI Detection AI tools can detect and fix this smell when you ask them to refactor unclear function names or enforce coding standards. They can analyze your entire codebase and suggest meaningful replacements for obfuscated names. Try Them! Remember: AI Assistants make lots of mistakes Try Them! Try Them! Remember: AI Assistants make lots of mistakes Remember: AI Assistants make lots of mistakes Remember: AI Assistants make lots of mistakes Without Proper Instructions

With Specific Instructions



ChatGPT

ChatGPT



Claude

Claude



Perplexity

Perplexity



Copilot

Copilot



Gemini

Gemini Without Proper Instructions

With Specific Instructions ChatGPT

ChatGPT Claude

Claude Perplexity

Perplexity Copilot

Copilot Gemini

Gemini Without Proper Instructions With Specific Instructions Without Proper Instructions Without Proper Instructions With Specific Instructions With Specific Instructions ChatGPT ChatGPT ChatGPT ChatGPT ChatGPT ChatGPT ChatGPT ChatGPT Claude Claude Claude Claude Claude Claude Claude Claude Perplexity Perplexity Perplexity Perplexity Perplexity Perplexity Perplexity Perplexity Copilot Copilot Copilot Copilot Copilot Copilot Copilot Copilot Gemini Gemini Gemini Gemini Gemini Gemini Gemini Gemini Conclusion Avoid obfuscating your function names. Write code that communicates your intent. When you prioritize readability, you make your software easier to understand, debug, and maintain. Cryptic code might look clever , but it adds unnecessary complexity. clever Related Reading https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xxviii https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xxviii https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xliii https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xliii https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-ii-o96s3wl4 https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-ii-o96s3wl4 https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-iv-7sc3w8n https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-iv-7sc3w8n More Info https://www.linkedin.com/posts/franco-aguilera-2583685a_the-code-challenge-scam-they-tried-to-hack-activity-7270114822950703107-K3DW/?embedable=true https://www.linkedin.com/posts/franco-aguilera-2583685a_the-code-challenge-scam-they-tried-to-hack-activity-7270114822950703107-K3DW/?embedable=true Disclaimer: Code Smells are my opinion. Disclaimer: Code Smells are my opinion . opinion Credits: Photo by Nikita Pavlov on Unsplash Credits: Photo by Nikita Pavlov on Unsplash Nikita Pavlov Unsplash The strength of a cryptographic system depends entirely on the strength of its weakest component. - Bruce Schneier The strength of a cryptographic system depends entirely on the strength of its weakest component. - Bruce Schneier - Bruce Schneier https://hackernoon.com/400-thought-provoking-software-engineering-quotes?embedable=true https://hackernoon.com/400-thought-provoking-software-engineering-quotes?embedable=true This article is part of the CodeSmell Series. This article is part of the CodeSmell Series. https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-i-xqz3evd?embedable=true https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-i-xqz3evd?embedable=true

This story contains new, firsthand information uncovered by the writer.

Refactoring 021 - Remove Dead Code

Refactoring 020 - Transform Static Functions

Buy My Book

Code Smell 284 - Encrypted Functions

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

10 Predictions About the Future of Finance

106 Stories To Learn About Clean Code

100 Pieces of Programming Advice from the Book Clean Code by Robert Martin

110 Stories To Learn About Refactoring

3 Things Coding And Prose Writing Have In Common According To Cory House

10 Predictions About the Future of Finance

106 Stories To Learn About Clean Code

100 Pieces of Programming Advice from the Book Clean Code by Robert Martin

110 Stories To Learn About Refactoring

3 Things Coding And Prose Writing Have In Common According To Cory House

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps