Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • A good read. Except this weird remark:

    "It used to be that if you could get a basic operating system coded and running, that was an indirect proof that you understood the basics of how operating systems worked."

    How many -- and we are even supposedly talking about students -- have coded an operating system and got it running?

  • Cloudflare says I'm not allowed to view the page. At least they are protected from "attacks."
  • by vdm
  • I love the "Tornado" term and "software debt"... worked with a few over the years, fixed the bug but broke the paradigm. Well articulated wisdom.
    by SA9G
  • > Software engineering is what happens to programming when you add time and other people.
  • Russ also has a great blog, with the most recent entry on fast floating-point printing and parsing. I believe these performance improvements have landed in the latest version of Go. https://research.swtch.com/fp
  • I recently learned that Russ also wrote software for The On-Line Encyclopedia of Integer Sequences (https://oeis.org) and is the president of the OEIS Foundation.
  • He puts words around what I've been feeling for the past 6 months or more:

    > Ousterhout introduces the term “tactical tornado” for a programmer who churns out tons of working but overly complex code that doesn’t fit well into the existing system. Worse, a bad manager often sees a tactical tornado as the most productive programmer on a team, failing to recognize the complexity and code debt left behind for the rest of the team to clean up. If we aren’t careful managers, AI agents can easily become the ultimate tactical tornadoes.

    by eka1

Explore Birbla archives