Roberto M. Morales
I'm an HVAC contractor in Miami. I've spent more than 20 years on service calls, in attics, on rooftops and inside electrical panels, and I write the books I wish someone had handed me in my first year.
I still run my company and still take calls. That's the basis of everything here: what I publish gets used on real equipment before it reaches a page.
How I learned this trade — and why I started writing about it
I started the way most technicians do: carrying gauges, following someone with more experience, and finding out fast that the manual rarely matches the attic. Miami is a hard place to learn cooling. Constant heat load, high humidity, salt air, and systems that never get a slow day. Equipment here shows its problems quickly, and so does a technician who is guessing.
I made the mistakes. I replaced parts that were never bad. I once chased a "bad compressor" that turned out to be a wiring problem I could have found in ten minutes with the right sequence. Those calls cost me money, and they cost me time standing in front of a customer with no answer. What changed my work wasn't a new tool. It was committing to an order of operations and refusing to skip a step.
Two decades later I run my own company: residential and light commercial service, installation and replacement, duct and airflow correction, electrical and control troubleshooting, and refrigerant-side diagnostics. Part of that job is training the technicians who work with me, and for years I kept drawing the same diagrams on the same scraps of paper for every new tech. One day I looked at a stack of those drawings and realized I had been writing a book without printing it.
So I wrote it, and then the next one. When a book of mine gives you a reading, a tolerance or a decision point, it's because that number settled an actual repair on an actual job.
"I don't want a technician to memorize my books. I want them to stop guessing — and to keep the money that guessing was costing them."
What I owe the technician holding the book
A misdiagnosis is never just a wrong answer. It's a part you paid for, a callback you drive back to on your own time, and a customer who starts to wonder whether you know what you're doing. Most of the technicians I've trained weren't careless. Nobody had ever taught them a method, so under pressure they reached for a guess.
What I try to do is simple: help you learn faster than I did, and help you avoid the expensive mistakes I already paid for. That means step-by-step teaching instead of theory alone, worked examples with real numbers, and diagrams big enough to read with a flashlight in your teeth. If a chapter can't hold up on a service call, it doesn't belong in the book.
Six rules every book has to pass
Most HVAC material is either too academic to use on a call or too shallow to solve anything. I write for the space in between: field-accurate, structured, and readable by a technician standing in front of a unit that will not run.
Write it so it reads in an attic
If a technician has to read a paragraph three times in a hot attic, I wrote it wrong. Short sentences, one idea at a time, and the drawing next to the words that explain it.
Technical accuracy, no shortcuts
Every reading, tolerance and sequence in my books came off real equipment. If I can't verify it in the field or against the manufacturer's data, it doesn't go on the page.
Practical application first
Theory matters when it changes what you do next. Each chapter ends where the work does: measure this, compare it to that, and here's the decision it points to.
A repeatable diagnostic order
Guessing costs parts, callbacks and trust. I teach a fixed sequence — verify, measure, compare, decide — so the same steps get you to the same answer in year one or year fifteen.
Books get revised
Equipment changes, codes change, and so do my books. Second editions exist because I keep finding better ways to explain something I already published.
Reader feedback shapes the next book
Technicians write to me about the part that finally clicked and the part that didn't. That decides what gets rewritten, what gets a bigger diagram, and what I write next.
Fewer guesses. Better technicians.
The trade loses time, parts and customers to guesswork. What I want is to put a clear, teachable diagnostic method in the hands of any technician who wants one: apprentices starting out, experienced techs shoring up a weak area, and owners training a crew.
Where I'm taking this catalog
HVAC technical education is the core of my work and it stays first. Everything else I publish is the same standard of clarity aimed at a different reader.
HVAC technical books
The core of the work, and where it stays. Airflow, electrical, refrigeration and full-system troubleshooting, with deeper diagnostic volumes and more Spanish-language editions on the way.
Artificial intelligence
Practical books on using AI as a working tool, written for people who want results rather than hype. Same plain-language standard, different subject.
Children's books
Stories that treat curiosity as normal. A kid who learns that taking something apart is a good instinct may end up in a trade one day.
Fiction
Where I write for the pleasure of it. It keeps my writing sharp, which shows up in the technical books too.
HVAC first — and a wider publishing platform
Start with the HVAC libraries below. That's where the depth is. The rest of the catalog is listed underneath if you want to see what else I write.
HVAC libraries
For the working technician and engineer.
BrowseThe clearest on-ramp into the trade.
BrowseUnderstand and protect your home.
BrowseOther publishing worlds
Let's find the right book for where you are
First-year tech, experienced installer working on a weak area, or an owner training a crew, there's a title for each. Browse the library, or tell the AI Concierge what you're stuck on and it will point you to the right one.