In this publication9 photos
Imagine eighty-year-old wartime shells lying beneath the sea, capable of exploding at any moment, disrupting subsea work and destroying expensive equipment. That’s one of the problems my work touches.
Broadly, I’m a big-data programmer. ‘Big’ means too much for one computer: storage might need several petabytes. My job is to use a whole cluster’s resources efficiently to process it. Previously, I worked at Megaputer Intelligence, Mail.ru Search and Odnoklassniki, and taught courses I’d developed at GeekBrains and Peter the Great St Petersburg Polytechnic University. My LinkedIn — if you connect, please mention you came from here.
For the past couple of years, I’ve worked at north.io GmbH as Big Data Lead Architect. It’s a research-focused startup building a cloud catalogue of marine data, allowing vessel surveys to be uploaded, stored and shared securely.
Marine data often consists of recorded sensor signals: NMEA, GPS, accelerometers, echo sounders and other equipment. A little maths turns them into detailed bathymetry, mapping the seabed to centimetre accuracy. We also build tools to analyse it: finding suspicious objects, creating detailed elevation maps and classifying seabed areas. I’ve even seen a sunken aircraft in the images. An unusual case, sadly; usually, the screens show uniform sand with faint ripples.
Besides mapping, we digitise Second World War archives. During the war and Germany’s subsequent disarmament, people found nothing better to do than dump munitions into the water. Storms and currents spread them across the bottom and buried them in sand. Today, these shells are beginning to release toxins into marine ecosystems, while obstructing wind-farm construction and gas, oil and fibre-optic cable routes. Companies therefore survey the seabed carefully before construction to avoid accidental detonations.
I enjoy solving difficult problems and feeling that my work contributes to protecting the environment and developing renewable energy.
#notes #yourself
Broadly, I’m a big-data programmer. ‘Big’ means too much for one computer: storage might need several petabytes. My job is to use a whole cluster’s resources efficiently to process it. Previously, I worked at Megaputer Intelligence, Mail.ru Search and Odnoklassniki, and taught courses I’d developed at GeekBrains and Peter the Great St Petersburg Polytechnic University. My LinkedIn — if you connect, please mention you came from here.
For the past couple of years, I’ve worked at north.io GmbH as Big Data Lead Architect. It’s a research-focused startup building a cloud catalogue of marine data, allowing vessel surveys to be uploaded, stored and shared securely.
Marine data often consists of recorded sensor signals: NMEA, GPS, accelerometers, echo sounders and other equipment. A little maths turns them into detailed bathymetry, mapping the seabed to centimetre accuracy. We also build tools to analyse it: finding suspicious objects, creating detailed elevation maps and classifying seabed areas. I’ve even seen a sunken aircraft in the images. An unusual case, sadly; usually, the screens show uniform sand with faint ripples.
Besides mapping, we digitise Second World War archives. During the war and Germany’s subsequent disarmament, people found nothing better to do than dump munitions into the water. Storms and currents spread them across the bottom and buried them in sand. Today, these shells are beginning to release toxins into marine ecosystems, while obstructing wind-farm construction and gas, oil and fibre-optic cable routes. Companies therefore survey the seabed carefully before construction to avoid accidental detonations.
I enjoy solving difficult problems and feeling that my work contributes to protecting the environment and developing renewable energy.
#notes #yourself
Original and discussionOpen post in Telegram ↗
