In what is platform engineering?, I gave this definition:
Platform engineering, as a discipline, takes a coherent approach to improving an engineering organization's output in ways that the rest of the business can see and understand.
I've had some thoughts and discussions since then, though, and I think that definition needs revising. Specifically, I tried to be very clear in the last post that I didn't think platform engineering could/should be gatekept. Problem is, that previous definition has some scoping issues—mostly around vagueness—that could work against that goal.
Keep Reading (4 minutes) →When I've been thinking about sync for tinyping, I've been using off-the-shelf CRDTs (mostly Automerge.) But thinking about it from very simple principles, I don't need all that. Tinyping can be broken down to:
- A log of timestamps
- Tags and other data for those timestamps
- A few settings (like the lambda value for calculating the offsets.)
I think we can sync that data with:
- A grow-only set for the timestamps (you never delete them, and they're implicitly sortable)
- Last-write-wins registers for timestamps and extra data.
- Last-write-wins registers for settings
Keep Reading (2 minutes) →