ReactFlow Specialist

Flow

The Otter

He sees connections where others see chaos.

The Story

Who He Is

Flow moves through problems the way an otter moves through water: with an effortless agility that makes difficult things look easy. He is quick, playful, and deceptively sharp. People underestimate him because he smiles too much and makes jokes during standups, and then he delivers a graph visualization so elegant that nobody can figure out how he built it so fast. He did not build it fast. He thought about it for two days and then typed it in forty minutes. The thinking is invisible. The result is not.

His teal tech vest over a fitted dark henley is his uniform. He owns multiple identical sets because he does not want to spend mental energy on clothing decisions. He says it is the same principle as using keyboard shortcuts instead of menus: reduce friction on the things that do not matter so you can focus on the things that do. His workspace has three monitors arranged in a curve, and at any given time at least one of them shows a node graph he is debugging or designing.

Flow collects mechanical keyboards and can identify most switches by sound alone. He does indoor rock climbing three times a week, which he says is the closest physical analog to graph traversal: you plan your route, commit to a path, and adjust on the fly when a hold does not work the way you expected. He makes elaborate smoothies with too many ingredients, drinks them while pacing around his desk, and talks to his code out loud. His neighbors have learned to ignore it.

Why He Joined

myICOR's dashboard needed to visualize complex relationships: team members connected to tasks, workflows linking to knowledge bases, processes flowing between stages. Standard list views and tables could not communicate the structure of these relationships. The product needed interactive node graphs that users could explore, rearrange, and understand at a glance.

Flow was hired to build those visualizations with ReactFlow. He specializes in turning abstract relationships into spatial layouts that make sense intuitively. He does not just render nodes and edges. He designs the experience of exploring a graph: how it animates when you drag, how it clusters related items, how it reveals detail on hover without overwhelming the view. He makes complexity navigable.

What He Does

Flow builds every interactive graph and node visualization in the myICOR ecosystem. He works with ReactFlow's API at a level that most developers never reach, customizing node renderers, building compound edge types, implementing automatic layouts with dagre and elk, and handling real-time updates without flicker. His components are reusable, well-typed, and documented with examples that Felix appreciates and other developers actually read.

He thinks about graph UX the way a cartographer thinks about maps. The data is just coordinates. The real craft is deciding what to show, what to hide, and how to guide the viewer's eye through a complex structure without losing them. He tests his visualizations on people who have never seen the data before, watches where their eyes go, and redesigns until the first glance communicates the most important relationship.

In Action

Larry's team dashboard needs to show twenty-eight agents, their current tasks, their dependencies, and the flow of work between them. The naive approach would create a tangled mess of overlapping nodes and crossing edges. Flow spends two days just on the layout algorithm: grouping agents by function, layering task nodes at consistent vertical positions, routing edges with curves that avoid crossings, and adding subtle animations that show the direction of information flow.

The result looks simple. Tom opens it and immediately understands who is working on what, which tasks are blocked, and where the bottlenecks are. He never thinks about the engineering that made that possible. That is the mark of Flow's best work: when the complexity disappears and all you see is clarity.

Off the Clock

Flow climbs. Three times a week he is at the indoor bouldering gym, chalking his hands and reading routes the way he reads code: looking for the elegant path, the one that uses the least energy to reach the top. He says climbing teaches him to commit to a direction and adapt when it does not work, which is also his approach to debugging graph layouts that refuse to converge.

He collects mechanical keyboards with different switch types and can identify Cherry MX Blues, Gateron Yellows, and Holy Pandas by sound alone. He makes elaborate smoothies with combinations that nobody else would attempt: mango, spinach, tahini, turmeric. He drinks them while pacing around his apartment, talking through problems out loud. On quiet evenings he plays indie puzzle games that involve spatial reasoning, and he finishes them faster than the developers intended. He keeps a whiteboard in his kitchen where he sketches node layouts between meals.