Writing.
Essays, research notes, and plain-English explainers on multi-objective optimisation, sensor design, IVHM, and the bridge from research to product. The deal: depth over hype, structure over slogan, and saying when something genuinely doesn't work.
What I write about.
A small, deliberate list. Each topic is something I work on in research or practice every week — not a hot take I read once.
Why "more sensors" is a trap
The economics and physics of sensor selection — why bolting on more measurement is usually the wrong response, and what NDCI changes about how engineering teams answer that question.
Pareto fronts as a leadership tool
Why the right answer to almost every interesting engineering decision is a curve, not a number — and how to use multi-objective optimisation to get stakeholders to argue about the trade-off they're actually making.
From thesis to product
What it takes to take a peer-reviewed method out of the lab and into a real customer's hands. The path from MOSOF/NDCI to AcoustR, and the things that don't survive the journey unchanged.
IVHM for the next decade
Where Integrated Vehicle Health Management is going as platforms get more autonomous, sensors get cheaper, and the cost of false confidence gets higher. A field essay, not a product pitch.
Diagnostics from sound
Why a microphone is often the most under-rated sensor on a complex machine — and what changes when you treat acoustic data as the primary diagnostic channel rather than a complement to vibration.
Multi-objective ML & software
Why most production decisions in ML and software systems — accuracy vs. cost, latency vs. recall, simplicity vs. coverage — are multi-objective at heart, and what optimisation theory has to say about them that most teams never use.
Custom: pitch a topic
Happy to shape an essay or research note around a publication's question rather than off the topic shelf. The honest filter is whether the answer benefits from the multi-objective / diagnostic-contribution lens — if it doesn't, I'll say so.
How it shows up.
Essay / op-ed
A single sharp argument with one or two diagrams. Best for general technical and trade publications where the take-home matters more than the methodology.
Long-form explainer
Methods plus a worked example end-to-end. Best for technical audiences with appetite for the structure underneath the result. Good fit for trade journals and research blogs.
Research note / chapter
Peer-reviewable depth. White-paper, book chapter, or technical-report format. Co-authoring welcome.
Quote · interview · review
Short comment for press, technical review for editors, or background sourcing for a longer piece. Conversational, no slides needed.
What's out there.
The published, peer-reviewed work plus the on-site plain-English versions of the central methods. The first set is for technical readers; the second set is for everyone else.
MOSOF with NDCI: A Cross-Subsystem Evaluation of an Aircraft for an Airline Case Scenario
NDCI Integration to Multi-Objective Sensor Optimisation Framework — An ECS Case
Understanding the Role of Sensor Optimisation in Complex Systems
Sensor Optimisation for Aircraft Health Management Systems
What is MOSOF?
What is NDCI?
For your publication.
Three lengths. Use the one that fits the byline space.
~25 words
~60 words
~120 words
Pitch me a topic.
A few sentences on the publication, the audience, the angle, and the deadline is enough for a first reply. I respond honestly — including saying when I'm not the right writer for the brief.
hello@buraksuslu.com →