71 / Coping with Copilot

✌🏻

Tweet of the Week

hot tip: to avoid writing bugs, don't write software — @FormalFerris on Twitter

Culture

• First Focus. Then Simplify (cutlefish.substack.com)

  John Cutler about the different approaches of simplifying a complex problem vs. focussing on a subset.

• The False Trade-off between Quality and Speed (maruz.medium.com)

  Mario Caropreso about the importance of quality in software development.

Tech

• Inside the Pinecone (pinecone.io)

  Edo Liberty about the experience of moving a C++ codebase to Rust.

• How to deal with money in software (cs-syd.eu)

  Tom Sydney Kerckhove about the right and wrong ways to deal with money in software.

• Fixing Memory Exhaustion Bugs in My Golang Web App (mtlynch.io)

  Michael Lynch tells the story of finding the cause(s) of OOM in a Go application.

• Why your website should be under 14kB in size (endtimes.dev)

  Nathaniel about the magic 14kB, the size transmitted on the first TCP roundtrip.

• Coping with Copilot (sigarch.org)

  Emery Berger about GitHub Copilot in education.

Cutting Room Floor

• "We Kill People Based on Metadata" and Other Metadata Things (darknetlive.com)

  A blogpost with software recommendations for dealing with metadata.

• A Shape of Things to Come (robinsloan.com)

  Robin Sloan about a weird discovery on Spotify.

• Good conversations have lots of doorknobs (experimentalhistory.substack.com)

  Adam Mastroianni about givers and takers and how to have good conversations.

• Using GPT-3 to augment human intelligence (escapingflatland.substack.com)

  Henrik Olof Karlsson explains how you can use AI language models (like GPT-3) to find answers that are hard to google.