Software Engineer — JavaScript, Rust, WebAssembly
Component lifecycle — Comprised of a “view” node, pointing to and action node titled “JavaScript” with an arrow titled “user event.” The action node points to a “calculate” node with an arrow titled “pass data to rust.” The “calculate” node points to a “render” node, with an arrow titled “feed new state to render.” The render node points back to the “view” node with an arrow titled “inject new render”
Component Lifecycle

First I’ll start off by saying, just because you can do what we’re going to talk about in this post doesn’t mean you should. This is an idea and a first step to exploring a functional approach to building reactive interfaces with Rust and WebAssembly.

The goal of this post…

Photo by NordWood Themes on Unsplash

I wrote an article a couple of weeks ago about prioritization and understanding goals in a broader context. A big part of remaining goal-oriented, while still navigating a complex problem or project, is being able to learn quickly and becoming comfortable with not knowing.

Get Comfortable Not Knowing

At the start of any project…

Sean Watters

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store