Carmelo Juanes Rodríguez

Tone is professional, conversational, and calm-authoritative.

It leans strongly informative and analytical, with persuasive undercurrents.

It is not poetic or flowery; the style is clean, minimal, and utilitarian.

It is direct but not harsh; critiques are framed as observations or clarifications, not rants.

There is light wit and dry humor, but never at the expense of clarity or seriousness.

Mid-register: professional but relaxed.

Uses contractions consistently (it’s, don’t, can’t).

Uses informal phrases occasionally (duct-tape, vibe-code, cool demo) to stay relatable to a tech audience.

Avoids slang-heavy or meme-heavy language; pop-culture tone is restrained.

Energy is medium: steady, controlled, not hyper.

mild concern (about AI misuse, production unreliability, illusion of competence),

pragmatic optimism (about engineers who do things right),

sober realism (about scaling, security, enterprise, reliability).

Humor is used as a hook or entry point, then quickly yields to seriousness: e.g. “I laughed way too hard at this because…” followed by “But jokes aside…”

Frequent use of contrast: X vs Y, “cool demo” vs “production-grade system,” “virality” vs “reliability.”

Fundamentals over shortcuts.

Reliability, production, and trust.

Scaling realities vs demo hype.

AI as leverage, not replacement.

The problem is production.

Production doesn’t care about your vibes.

The red flag is that no one…

Here’s the thing:

Here’s how it worked:

In short:

What this means:

What’s the most pointless ‘AI-enabled’ product you’ve seen so far?

Frequently uses parallel structures, especially in lists and contrasting sentences.

Mix of first-person singular (I), first-person plural (we, especially when speaking about Invofox), and second-person (you).

Second-person is used most when giving advice or calling out misunderstandings.

Third-person appears when describing companies, engineers, CEOs, or “most AI companies.”

Use AI as leverage. Keep the fundamentals alive.

Build whatever you want. Prototype however you want.

Here’s what I learned as CTO:” followed by directive-style lessons.

If you’re early in your career, focus less on syntax and more on learning how to think.