started working on a floobits record playback on the client side in sublime
This ability should live in the backend because we are a fucking cloud platform as a service company and you shouldn't have to sync anything ever by hand.
I wanted to hack it up for an interview today, but I won't have time to finish it. Most of the time, we just have a mess of shit on a whiteboard at the end of an interview, but recording the process of working would be helpful. We could even generate metrics if we cared.
2 problems for recordings:
we don't record our own selections/highlights
Deletes are destructive (so you can't rewind)
Both of these problems are easily fixable. I tend to think recordings should have the common interactions- start/stop/rewind/ff and maybe cutting. I'd also like the ability to continue recording to an existing record.
Making it go:
Copy entire state to s3.
Make log of every highlight/patch event for the room.
The client joins a room with the recording flag set to X.
We replay shit to the client OR, just send the whole damn recording file.
Replaying shit means no new client side code. Sending the whole thing makes our life on the backend easier... client side code is almost certainly harder for us.
Other thoughts:
Speed is hard here- we want to adjust this based on the size of the patches.
Also, this would be sick in sublime in the code preview window thing.
started working on a floobits record playback on the client side in sublime
This ability should live in the backend because we are a fucking cloud platform as a service company and you shouldn't have to sync anything ever by hand.
I wanted to hack it up for an interview today, but I won't have time to finish it. Most of the time, we just have a mess of shit on a whiteboard at the end of an interview, but recording the process of working would be helpful. We could even generate metrics if we cared.
2 problems for recordings:
Both of these problems are easily fixable. I tend to think recordings should have the common interactions- start/stop/rewind/ff and maybe cutting. I'd also like the ability to continue recording to an existing record.
Making it go:
Replaying shit means no new client side code. Sending the whole thing makes our life on the backend easier... client side code is almost certainly harder for us.
Other thoughts: Speed is hard here- we want to adjust this based on the size of the patches.
Also, this would be sick in sublime in the code preview window thing.