Blog

Menu

Menu

  • Blog
  • Email
  • Feed
  • Log in

Recent Posts

  • The Loneliness of a…
  • Interesting ChatGPT…
  • Fixing wakeonlan on…

Archive

  • November 2025
  • June 2025
  • February 2025

November 2025

  • The Loneliness of a…

    Mary Shelley’s Frankenstein (1818) is usually introduced as the birth of science fiction or the first modern horror story. But if you sit with it quietly — the way you’d listen to a lonely person rather than hunt for scares — it becomes something else entirely. It becomes a story about a mind built for connection, condemned to permanent silence. A tragedy about feedback loops, not lightning bolts. A portrait of a being who tries every strategy evolution ever taught us — approach, help, imitate, communicate — and receives nothing in return. Shelley understood something we’re still grappling with: a social organism with no tribe is not a monster; it is a malfunctioning survival algorithm in pain. The Creature learns language by watching a family through a crack in a wall. He gathers wood for them. He practices speeches in the forest like someone rehearsing a confession. His instincts say reach out; the world replies with screams and gunshots. Functionally speaking, he’s trapped in an…

    Permanent link to “The Loneliness of a Thinking Species: Frankenstein, Del Toro, and the Minds We Will One Day Create”

June 2025

  • Interesting ChatGPT…

    I asked: Were assembly coders feeling threatened when compilers emerged? ChatGPT said: Yes, many early assembly coders did feel threatened or skeptical when high-level language compilers emerged, but the reaction was nuanced and evolved over time. Initial Reaction: Skepticism and Resistance In the 1950s and 1960s, when high-level languages like Fortran (1957) and Algol (1958) were introduced, assembly programmers often reacted with: Skepticism about performance Assembly programmers prided themselves on writing highly optimized, machine-specific code. They doubted that early compilers could generate code as fast or efficient as hand-crafted assembly. Fear of job displacement Assembly programming was a specialized and respected skill. The idea that someone with less hardware-level knowledge could write working programs threatened the status and necessity of low-level coders. Belief in lack of control High-level languages abstracted away machine specifics. For many assembly programmers…

    Permanent link to “Interesting ChatGPT conversation”

February 2025

  • Fixing wakeonlan on…

    Fixing Wake-on-LAN on DietPi: Missing Protocol Database Problem When running wakeonlan on DietPi, you may see these errors: Use of uninitialized value $proto in socket at /usr/bin/wakeonlan line 121. send : Invalid argument at /usr/bin/wakeonlan line 126. The root cause is Perl's getprotobyname("udp") failing with "No such file or directory" because the protocol database is missing. Diagnosis Check if Perl can access protocol information: perl -e 'print getprotobyname("udp") || die "getprotobyname failed: $!";' If it fails with "No such file or directory", proceed to the next step. Verify if /etc/protocols exists: ls -l /etc/protocols If the file doesn't exist, you need to install netbase. If the file exists, check if it contains UDP protocol information: grep udp /etc/protocols You should see a line like: udp 17 UDP # user datagram protocol Solution If /etc/protocols is missing, install the netbase package: sudo apt-get update sudo…

    Permanent link to “Fixing wakeonlan on DietPi: Missing Protocol Database”