Read the spec, then go see if it works
Quote
implementing a protocol is always an exercise I in reading and reverse engineering, you have to read the spec to understand it enough to begin the process of doing the thing, but that's not enough. It'll never be enough. You'll never blindly write a rhotic write things to a spec. Step two is always go see if it works.
Episode 155: Landing Zone (episode page, opens in a new tab) 00:49:52 (play audio from this timestamp, opens in a new tab)
Speaker-labeled
Summary
Implementing a protocol is always reading plus reverse engineering. The spec alone is never enough, so step two is always testing against reality.
Also said
Episode 133: It's a Lifestyle! (episode page, opens in a new tab) 00:58:27 (play audio from this timestamp, opens in a new tab)
If you say if you think you have a good solution, start delivering that solution, if it's not too much trouble, and then we'll all start playing with it.
Speaker-labeled
Episode 162: Unwise Unwrap (episode page, opens in a new tab) 00:38:21 (play audio from this timestamp, opens in a new tab)
the loose rule was always we need at least one host at least one app to implement it.
Speaker-labeled