About / Kian + TranquilWorks
A systems view of small tools
I am a systems and software engineer working across hardware, firmware, test, and the awkward boundaries between them, while completing graduate study in electrical engineering.
This public biography deliberately omits employer, program, location, and sensitive work details. Personal disclosure is an owner-controlled publication decision.
TranquilWorks exists because capable tools are often trapped behind the wrong cost, the wrong interface, or the assumption that every small lab has an integration team.
The connective tissue is often the product.
I am interested in the layer between an instrument and a useful workflow: control, fixtures, repeatability, data, documentation, and the recovery path when something fails.
The work extends beyond the bench into controls, robotics, vehicle dynamics, racing, photography, and the systems used to learn them. That breadth is intentional. A product earns trust when the electrical, mechanical, software, operational, and human pieces survive contact with each other.
The standard is not maximal performance. It is the right performance, at a cost and complexity that lets another person understand, repair, and extend the result.
Start a conversationOperating principles / v1
Make the complicated thing legible.
- 01
Design for the job
Preserve the capability that changes a real workflow. Remove the cost that does not.
- 02
Show the boundary
Concept, simulation, protocol fixture, and physical validation are different states—not marketing synonyms.
- 03
Leave a way back
Source, schematics, rollback, and repair information belong in the product definition.