I built an ROV to solve missing person cases

Original Article ↗ Hacker News Discussion ↗

Article format and accessibility

  • Many note the story is split into 13+ pages and wish it were a single, continuous article.
  • Some share workflows to “stitch” the pages (e.g., web clippers + SQL + Calibre), while others say the pagination is tolerable with normal page-turning.
  • The series is widely described as long but gripping; several people who don’t usually read long pieces say they read it all.

Technical and robotics discussion

  • Comments highlight the impressive DIY build: side-scan sonar boat plus underwater ROV, all from scratch, for a fraction of commercial costs.
  • Others point out comparable off‑the‑shelf ROVs exist and may be cheaper once failed parts and time are considered, but still praise the effort and learning.
  • Specific technical points: controller joystick precision issues, potential long‑range radio upgrades (ELRS), consideration of wireless vs tethered links, and a suggestion to add a magnetometer.
  • Several discuss the difficulty of autonomous underwater mapping (currents, drift, lack of GPS), contrasting human‑piloted ROVs with AUV/UUV systems and citing academic swarm‑robotics work.

Search, rescue, and investigation themes

  • A linked earlier SAR story (“Death Valley Germans”) is repeatedly recommended; it inspired both the author and some commenters to join SAR teams.
  • One SAR volunteer describes real-world fitness tests and emphasizes the physical demands and teamwork.
  • Some criticize police for not reasoning as systematically as the hobbyists and for initially dismissive reactions; others argue hindsight bias, limited resources, and misleading witness reports make this unfair.
  • There is speculation about whether one case was suicide vs accident, and brief discussion of how bodies behave in water, but details are acknowledged as incomplete or sensitive.

Acronyms, jargon, and communication

  • Many complain that “ROV” isn’t defined early in the article; others respond that readers can easily look it up.
  • This sparks a broader debate: one side argues acronyms are a real barrier for general audiences; the other defends jargon as efficient for knowledgeable readers.
  • A few mention small tooling niceties (OS features, HTML abbreviation tags) for quickly resolving unfamiliar terms.

Overall reception and impact

  • The thread is overwhelmingly enthusiastic: numerous comments call it one of the best or most “HN‑core” reads in years.
  • People praise the blend of detective work, engineering, persistence, and humility, and several say it inspired them to consider SAR work or building their own ROVs.
  • Multiple commenters think the story is strong enough to become a documentary or miniseries.