He handed her the USB drive with the project files. As she walked away, he opened CivilCAD’s about screen: Versão 2016.2 (x64) – Memória máxima teórica: 16 EB . He laughed softly. He would never need that much memory. But knowing it was there—that was engineering peace of mind.
Rodrigo’s only lifeline was CivilCAD 2016—64-bit version.
“Trust me,” she had said, installing the 64-bit build from a USB drive labeled CivilCAD_2016_x64_Final . “More memory. Less tears.”
“CivilCAD 2016,” he said. “The 64-bit one.”
He had resisted upgrading for months. His old 32-bit setup crashed whenever he tried to process more than 8,000 alignment points. But after a catastrophic blue screen the previous week, his IT manager, a sharp-eyed woman named Helena, had forced the switch.
The triangulated surface appeared in 3D, colored by elevation: blues in the low-lying creek beds, reds on the unstable hillsides. Rodrigo rotated the view. No lag. No crashes.
He whistled. 64-bit , he thought. Finally.
Near sector 7 of the survey, a series of points formed a perfect arc—not natural terrain. He zoomed in. The coordinates suggested an abandoned concrete foundation, undocumented in the original geotechnical report. If he built the drainage channel over it without mitigation, the structure could crack within two years.
Rodrigo looked at the water flowing calmly through the concrete channel. “Sometimes,” he replied, “the right tool doesn’t need to be new. It just needs to work when everything else fails.”
By 4:00 AM, Rodrigo had redesigned the channel’s alignment, shifting it 14 meters north to bypass the old foundation. CivilCAD recalculated cut-and-fill volumes in 11 seconds. He generated longitudinal profiles, cross-sections at every 20 meters, and a runoff simulation that accounted for a 1-in-100-year storm.
Then he noticed something odd.
Rodrigo took a sip of coffee. “Not one.”
