Hi, this is Anandhu Prakash.

I'm an embedded engineer working on the kind of systems that have to survive without anyone there to fix them.

For the last few years I've been writing automotive software — the paranoid, methodical world where a missed timing requirement is felt as a different brake pedal, and where shipping is measured in months of validation. I'm pivoting that craft toward harder environments: the deep ocean and low Earth orbit, where the same engineering language (pressure, thermal, radiation, vibration, latency, autonomy under partial information) gets weirder and more interesting.

Subsea Signals is where I write the work down — case studies of what I'm building, build journals from what's still rough, and lab notes on the topics I'm being forced to learn.

A few things I've come to believe about engineering for extreme environments:

• The interesting failures happen at the boundary between domains — software meeting hardware meeting fluid meeting metal.
• Build journals beat finished case studies. The path matters more than the polish.
• There are no clean abstractions where pressure differentials are involved.
• The field teaches you more in a week than the lab does in a month — but the lab is where you earn the right to go to the field.
• Working in public is the correction loop. You can't get one as a stranger on the internet correcting you if there's nothing for them to correct.