Jackson Hardaker's Avatar

Jackson Hardaker

@jacksonhardaker

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

12
Followers
6
Following
6
Posts
07.11.2024
Joined
Posts Following

Latest posts by Jackson Hardaker @jacksonhardaker

Video thumbnail

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! ๐Ÿš€

09.06.2025 21:22 ๐Ÿ‘ 4 ๐Ÿ” 3 ๐Ÿ’ฌ 0 ๐Ÿ“Œ 0

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

09.05.2025 15:06 ๐Ÿ‘ 1 ๐Ÿ” 0 ๐Ÿ’ฌ 0 ๐Ÿ“Œ 0
Preview
Reality check: OpenTelemetry is not going to solve your observability woes - bitdrift Blog

Spicy Tuesday take from me:

blog.bitdrift.io/post/reality...

04.02.2025 22:29 ๐Ÿ‘ 10 ๐Ÿ” 3 ๐Ÿ’ฌ 1 ๐Ÿ“Œ 0
Video thumbnail

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. ๐Ÿ˜‰

30.01.2025 17:30 ๐Ÿ‘ 8 ๐Ÿ” 3 ๐Ÿ’ฌ 2 ๐Ÿ“Œ 0

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.

22.11.2024 21:47 ๐Ÿ‘ 0 ๐Ÿ” 0 ๐Ÿ’ฌ 0 ๐Ÿ“Œ 0
<ComparisonProvider>
  <ComparisonProvider.Treatment>
    <Chart range="7d-14d"/>
  </ComparisonProvider.Treatment>
  <ComparisonProvider.Control>
	  <Chart range="now-7d"/>
  </ComparisonProvider.Control>
</ComparisonProvider>

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

๐Ÿงต 4/4

End result looks something like:

22.11.2024 21:06 ๐Ÿ‘ 0 ๐Ÿ” 0 ๐Ÿ’ฌ 1 ๐Ÿ“Œ 0

๐Ÿงต 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.

22.11.2024 21:06 ๐Ÿ‘ 0 ๐Ÿ” 0 ๐Ÿ’ฌ 1 ๐Ÿ“Œ 0

๐Ÿงต 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.

22.11.2024 21:06 ๐Ÿ‘ 0 ๐Ÿ” 0 ๐Ÿ’ฌ 1 ๐Ÿ“Œ 0

๐Ÿงต 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

22.11.2024 21:06 ๐Ÿ‘ 1 ๐Ÿ” 1 ๐Ÿ’ฌ 1 ๐Ÿ“Œ 0
Video thumbnail

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? ๐Ÿš€

05.11.2024 22:55 ๐Ÿ‘ 8 ๐Ÿ” 4 ๐Ÿ’ฌ 2 ๐Ÿ“Œ 0