HTML MASTER CLASS /// LEARN TAGS /// BUILD STRUCTURE /// SEMANTIC WEB /// HTML MASTER CLASS /// LEARN TAGS ///

Untitled Lesson

⚡ Total XP: 0|💻 backend XP: 0

Skill Matrix

UNLOCK NODES BY LEARNING NEW TAGS.

Select an unlocked node to view details root

Pascual Vila

Frontend Instructor // Code Syllabus

Common Pitfalls & Errors

The Error //

Logging sensitive data (passwords, tokens, full credit card numbers) in plaintext

// Wrong
logger.info('Login attempt', req.body); // includes plaintext password

// Correct
const { password, ...safeBody } = req.body;
logger.info('Login attempt', safeBody);

The Solution //

Log entries often end up in third-party monitoring tools or long-retention storage that far more people can access than the production database itself. Redact or omit fields like password, authorization, and token before logging any request/response object.

The Error //

Using console.log as the only error visibility in production

// Wrong: console.log('DB connection failed');
// Correct: logger.error({ msg: 'DB connection failed', err });

The Solution //

console.log output disappears the moment a container restarts or a process crashes, and it isn't queryable at scale. Use a structured logger (Winston, Pino) that writes JSON to a persistent destination (file, external log aggregator) so failures are still visible after the process is gone.