Network header endianness mismatch
An AI generated this Rust code to serialize a port number and sequence value into a fixed network header before sending. It compiles and round-trips fine in the same process. Explain why a peer on a different machine misreads the header, the trigger, and the fix.
Implement
write_wire_header(seq: int, port: int) → list[int]Examples
in
[1,80]out[0,0,0,1,0,80]in
[305419896,80]out[18,52,86,120,0,80]in
[0,20480]out[0,0,0,0,80,0]What a strong answer looks like
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.
0:00 of about 16 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.