67 / Your Code Doesn’t Have to Be a Mess

Hey hey, how was your week? ✌🏻

Tweet of the Week

Remember, a strong type system can prevent classes of bugs, but you still have to test to make sure your logic is correct. Rust, but Verify — @jckarter on Twitter

Culture

• The practical application of "Rocks, Pebbles, Sand" (longform.asmartbear.com)

  Jason Cohen about a strategy to plan software projects.

• Spell. It. Out. (codingvc.com)

  Leo Polovets on being clear in presentation and leave nothing up for interpretation.

Tech

• Your Code Doesn’t Have to Be a Mess (danielsieger.com)

  Daniel Sieger lists 5 strategies for good code.

• You should take more screenshots (alexwlchan.net)

  Alex Chan about taking screenshots of projects so you can explore them when it gets hard to get them running again.

• A toy remote login server (jvns.ca)

  Julia Evans wrote a toy login server and explains the basic technology.

• Library Writing Realizations (cbloomrants.blogspot.com)

  cbloom has 10 points of advice for writing libraries.

• Does Rust need proc-macros 2.0? (aaronerhardt.github.io)

  Aaron Erhardt about the current shortcomings of proc-macros in Rust.

• Fixing the Next Thousand Deadlocks: Why Buffered Streams Are Broken and How To Make Them Safer (blog.polybdenum.com)

  A blog post about some possible problems with Rust’s Buffered streams (e.g. because a future in the stream depends on another one).

Cutting Room Floor

• Your Kids Are Not Doomed (nytimes.com)

  Ezra Klein in an opinion piece about having kids in a world of crisis.

• Don't Panic (randsinrepose.com)

  Michael Lopp about the FromSoftware “Souls” games and what they teach you.

• The Best iPhone (notes.ghed.in)

  Rodrigo Ghedin explains why they think the iPhone SE is the best iPhone.