iiinova — where your digital self keeps evolving

Jackson Hardaker

@jacksonhardaker.bsky.social

past jazz musician - current software engineer (@bitdrift.io)

Jackson Hardaker @jacksonhardaker.bsky.social · 01/05/2026

In 20 years time, when people are looking to refer to individuals on the cusp of gen. alpha and gen. beta (i.e. what zennial is to millennial and gen. z) let it be known that I lay claim to the use of the term "alphabetical" for this purpose.

000

Reposted by Jackson Hardaker

Matt Klein @mattklein123.dev · 09/06/2025

Do you know what this teaser is? It's first party crash reporting support in @bitdrift.io Capture. Do you know what that means? Legacy mobile observability tools are about to be obsolete. So, so excited to ship this. Watch this space! 🚀

043

Jackson Hardaker @jacksonhardaker.bsky.social · 09/05/2025

That's right. We also use MUI as the underlying component library, xyflow for our workflow editor, and airbnb/visx for visual chart primitives .

010

Reposted by Jackson Hardaker

Matt Klein @mattklein123.dev · 04/02/2025

Spicy Tuesday take from me: blog.bitdrift.io/post/reality...

blog.bitdrift.io

Reality check: OpenTelemetry is not going to solve your observability woes - bitdrift Blog

1103

Reposted by Jackson Hardaker

Matt Klein @mattklein123.dev · 30/01/2025

Early prototype of bitdrift Capture running in the browser, including session replay. This is our Rust core compiled to WASM and executed. Still a lot to do, but very promising. Real-time dynamic observability coming to a browser near you. Get in touch if this sounds interesting. 😉

283

Jackson Hardaker @jacksonhardaker.bsky.social · 22/11/2024

In that snippet the "ComparisonProvider.Treatment" context has access to the treatment tooltip position setter, and the control getter, while "ComparisonProvider.Control" has access to the control setter, and the treatment getter.

000

Jackson Hardaker @jacksonhardaker.bsky.social · 22/11/2024

🧵 4/4 End result looks something like:

<ComparisonProvider>
<ComparisonProvider.Treatment>
<Chart range="7d-14d"/>
</ComparisonProvider.Treatment>
<ComparisonProvider.Control>
<Chart range="now-7d"/>
</ComparisonProvider.Control>
</ComparisonProvider>

100

Jackson Hardaker @jacksonhardaker.bsky.social · 22/11/2024

🧵 3/4 Problem 3: Expose the setter/getter to the relevant chart. Solution: Add two variants of a nested context which exposes getter A / setter B, and getter B / setter A.

100

Jackson Hardaker @jacksonhardaker.bsky.social · 22/11/2024

🧵 2/4 Problem 2: Prevent changes in your new context propagating back to the chart component which dispatched the change. Solution: Track the tooltip position for each chart separately, splitting the context to expose the setter/getter separately.

100

Jackson Hardaker @jacksonhardaker.bsky.social · 22/11/2024

🧵 1/4 Build a comparison view while reusing your existing chart component. Problem 1: Sync tooltip position between two separate charts. Solution: Wrap in a context to track the tooltip position (when it is displayed), reading the position back into the other chart. #react

111

Reposted by Jackson Hardaker

Matt Klein @mattklein123.dev · 05/11/2024

Real-time observability Tuesday: the best session replay for mobile is about to get a lot more exciting! Now take on-demand pixel screen shots based on workflow rules. Want to see exactly what the user is seeing when something specific happens? 🚀

284