<?xml version="1.0" encoding="UTF-8"?>
<rss
  version="2.0"
  xmlns:dc="https://purl.org/dc/elements/1.1/"
  xmlns:sy="https://purl.org/rss/1.0/modules/syndication/"
  xmlns:admin="https://webns.net/mvcb/"
  xmlns:rdf="https://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:content="https://purl.org/rss/1.0/modules/content/"
  xmlns:blogChannel="https://backend.userland.com/blogChannelModule"
  xmlns:atom="https://www.w3.org/2005/Atom"
>

<channel>
  <title>Diomidis D. Spinellis Web Log</title>
  <link>https://www.spinellis.gr/blog</link>
  <description>The Internet soapbox of Diomidis Spinellis</description>
  <dc:creator>dds</dc:creator>
  <dc:type>Text</dc:type>
  <dc:title>Diomidis D. Spinellis Web Log</dc:title>
  <dc:identifier>https://www.spinellis.gr/blog</dc:identifier>
  <dc:date>2004-08-20T18:00:00-03:00</dc:date>
  <dc:language>en</dc:language>
  <sy:updatePeriod>weekly</sy:updatePeriod>
  <sy:updateFrequency>2</sy:updateFrequency>
  <sy:updateBase>2003-01-01T12:00+00:00</sy:updateBase>
  <generator>blog.pl 3c6ad07 2025-12-24 23:55:57 +0200</generator>
  <docs>https://blogs.law.harvard.edu/tech/rss</docs>
  <atom:link href="https://www.spinellis.gr/blog/dds-blog-rss.xml" rel="self" type="application/rss+xml" />

  <image rdf:about="https://www.spinellis.gr/dds.gif">
    <title>Diomidis D. Spinellis Web Log</title>
    <url>https://www.spinellis.gr/dds.gif</url>
    <link>https://www.spinellis.gr/blog</link>
  </image>

  <item>
    <title>Empirical software research in the age of AI</title>
    <link>https://www.spinellis.gr/blog/20260413</link>
    <description>
 In a keynote presentation at the 2026 Mining Software Repositories
Emerson Murphy-Hill, a star researcher at Microsoft, presented his
view on the role of an empirical software engineering researcher in the age of generative AI.
His talk focused on three themes: the durability, differentiation, and
dissemination of research. 
</description>
    <guid isPermaLink="true">https://www.spinellis.gr/blog/20260413</guid> <!-- Hardcoded site here -->
    <dc:creator>Diomidis Spinellis</dc:creator>
    <dc:type>Text</dc:type>
    <dc:title>Empirical software research in the age of AI</dc:title> <!-- Hardcoded site here -->
    <dc:identifier>https://www.spinellis.gr/blog/20260413</dc:identifier>
    <dc:date>2026-04-13T14:06:11-00:00</dc:date>
    <dc:language>en</dc:language>
  </item>

  <item>
    <title>Vibe coding toward the incident horizon</title>
    <link>https://www.spinellis.gr/blog/20260302</link>
    <description>
 We are living through a golden age of generative AI: a time when progress is both breathtaking and somehow still unable to reliably open a PDF without hallucinating the author’s middle name. The curve is real, the funding is real, and the demos are so real that they must be watched on a stage with dramatic lighting, because ordinary lighting reveals too much. The modern model does many things remarkably well—summarization, translation, code generation—and then it will confidently assert that 9 is a prime number “depending on your threat model,” which is how you know you’re witnessing history. 
</description>
    <guid isPermaLink="true">https://www.spinellis.gr/blog/20260302</guid> <!-- Hardcoded site here -->
    <dc:creator>Diomidis Spinellis</dc:creator>
    <dc:type>Text</dc:type>
    <dc:title>Vibe coding toward the incident horizon</dc:title> <!-- Hardcoded site here -->
    <dc:identifier>https://www.spinellis.gr/blog/20260302</dc:identifier>
    <dc:date>2026-03-02T16:44:31-00:00</dc:date>
    <dc:language>en</dc:language>
  </item>

  <item>
    <title>An initial analysis of the discovered Unix V4 tape</title>
    <link>https://www.spinellis.gr/blog/20251223</link>
    <description>
 Several news outlets
 reported 
the  discovery of a 1970s Fourth Edition Research Unix magnetic tape 
at the University of Utah in July 2025 and its successful restoration.
This is a significant find, because up to now only
the Fourth Edition’s manual was thought to have survived.
Over the past few days I incorporated the tape’s source code into the
 Unix History Repository 
hosted on GitHub (see it  here )
and studied the code’s composition. 
</description>
    <guid isPermaLink="true">https://www.spinellis.gr/blog/20251223</guid> <!-- Hardcoded site here -->
    <dc:creator>Diomidis Spinellis</dc:creator>
    <dc:type>Text</dc:type>
    <dc:title>An initial analysis of the discovered Unix V4 tape</dc:title> <!-- Hardcoded site here -->
    <dc:identifier>https://www.spinellis.gr/blog/20251223</dc:identifier>
    <dc:date>2025-12-23T18:18:55-00:00</dc:date>
    <dc:language>en</dc:language>
  </item>

  <item>
    <title>Why I choose email over messaging</title>
    <link>https://www.spinellis.gr/blog/20250926</link>
    <description>
 My colleagues and friends know that I prefer to communicate
with them via email rather than chat messaging.
There are many benefits in such a choice.
You may want to consider them and adopt the same stance. 
</description>
    <guid isPermaLink="true">https://www.spinellis.gr/blog/20250926</guid> <!-- Hardcoded site here -->
    <dc:creator>Diomidis Spinellis</dc:creator>
    <dc:type>Text</dc:type>
    <dc:title>Why I choose email over messaging</dc:title> <!-- Hardcoded site here -->
    <dc:identifier>https://www.spinellis.gr/blog/20250926</dc:identifier>
    <dc:date>2026-03-02T16:47:22-00:00</dc:date>
    <dc:language>en</dc:language>
  </item>

  <item>
    <title>Is it legal to use copyrighted works to train LLMs?</title>
    <link>https://www.spinellis.gr/blog/20250626</link>
    <description>
 Two widely-reported court rulings in San Francisco
found that employing copyrighted works to train Large Language Models (LLMs)
fell within the law’s “fair use” provisions.
The fact that writers brought these lawsuits shows that they felt wronged
by the use of their works to train LLMs without their permission.
What should we make of those rulings? 
</description>
    <guid isPermaLink="true">https://www.spinellis.gr/blog/20250626</guid> <!-- Hardcoded site here -->
    <dc:creator>Diomidis Spinellis</dc:creator>
    <dc:type>Text</dc:type>
    <dc:title>Is it legal to use copyrighted works to train LLMs?</dc:title> <!-- Hardcoded site here -->
    <dc:identifier>https://www.spinellis.gr/blog/20250626</dc:identifier>
    <dc:date>2025-06-26T12:07:56-00:00</dc:date>
    <dc:language>en</dc:language>
  </item>

  <item>
    <title>I’m removing the BSD advertising clause</title>
    <link>https://www.spinellis.gr/blog/20250520</link>
    <description>
 Some open source software I wrote decades ago was distributed with the
then-current BSD license, which included an advertising clause.
This hinders the code’s reuse and distribution, so I’m hereby declaring
that the clause’s requirements no longer apply to my code, and
that the corresponding clause can be deleted from it. 
</description>
    <guid isPermaLink="true">https://www.spinellis.gr/blog/20250520</guid> <!-- Hardcoded site here -->
    <dc:creator>Diomidis Spinellis</dc:creator>
    <dc:type>Text</dc:type>
    <dc:title>I’m removing the BSD advertising clause</dc:title> <!-- Hardcoded site here -->
    <dc:identifier>https://www.spinellis.gr/blog/20250520</dc:identifier>
    <dc:date>2025-05-20T11:09:41-00:00</dc:date>
    <dc:language>en</dc:language>
  </item>

  <item>
    <title>The perils of GenAI student submissions</title>
    <link>https://www.spinellis.gr/blog/20250411</link>
    <description>
 Generative AI (GenAI) systems, such as ChatGPT,
can help students as their personal tutor,
by allowing them to study what interests them,
by providing in depth explanations to topics they didn’t quite understand,
by assessing their work and problems with it, and
by providing shortcuts to parts of their work that aren’t directly relevant
to what they want to learn.
However, students sometimes
misuse GenAI
to derive answers for work they were supposed to conduct on their own as part
of their learning,
or accept its answers uncritically.
For the first type of misuse part of the blame occasionally
also lies with educators
for giving out-of-class assignments that GenAI can perform with ease.
For the second type of misuse students must learn to avoid using
unverified GenAI output.
Needless to say that in both cases the misuse of AI may also constitute
academic fraud and violate their university’s code of conduct.
Here is my take on the practicalities of the two cases. 
</description>
    <guid isPermaLink="true">https://www.spinellis.gr/blog/20250411</guid> <!-- Hardcoded site here -->
    <dc:creator>Diomidis Spinellis</dc:creator>
    <dc:type>Text</dc:type>
    <dc:title>The perils of GenAI student submissions</dc:title> <!-- Hardcoded site here -->
    <dc:identifier>https://www.spinellis.gr/blog/20250411</dc:identifier>
    <dc:date>2025-04-11T03:31:35-00:00</dc:date>
    <dc:language>en</dc:language>
  </item>

  <item>
    <title>Unix make vs Apache Airflow</title>
    <link>https://www.spinellis.gr/blog/20241015</link>
    <description>
 In an  IEEE Software  “Adventures in Code” column titled
 Modular Data Analytics 
I describe the benefits and use of
 simple-rolap ,
a tool suite for relational online analytical processing.
I have built  simple-rolap  based on the Unix  make  tool and a few
shell scripts.
With  make  approaching its 50th birthday,
before writing the column
I looked for possible modern and better alternatives I might be ignoring. 
</description>
    <guid isPermaLink="true">https://www.spinellis.gr/blog/20241015</guid> <!-- Hardcoded site here -->
    <dc:creator>Diomidis Spinellis</dc:creator>
    <dc:type>Text</dc:type>
    <dc:title>Unix make vs Apache Airflow</dc:title> <!-- Hardcoded site here -->
    <dc:identifier>https://www.spinellis.gr/blog/20241015</dc:identifier>
    <dc:date>2024-10-15T11:19:35-00:00</dc:date>
    <dc:language>en</dc:language>
  </item>

  <item>
    <title>How (and how not) to present related work</title>
    <link>https://www.spinellis.gr/blog/20240805</link>
    <description>
 A key part in scientific writing is a description of related work.
This section establishes what is known in the given area
and the new publication’s contribution.
It also provides a signal to reviewers and readers regarding the study’s
innovativeness, credibility, and thoroughness.
A paper with a shallow related work section may well have overlooked
important relevant work that would have supported its theory building,
methods, or conclusions.
A mistake often made in related work sections is to present them as
a laundry list ( A  did  X ,  B  did  Y ), often in chronological order. 
</description>
    <guid isPermaLink="true">https://www.spinellis.gr/blog/20240805</guid> <!-- Hardcoded site here -->
    <dc:creator>Diomidis Spinellis</dc:creator>
    <dc:type>Text</dc:type>
    <dc:title>How (and how not) to present related work</dc:title> <!-- Hardcoded site here -->
    <dc:identifier>https://www.spinellis.gr/blog/20240805</dc:identifier>
    <dc:date>2024-08-05T10:43:27-00:00</dc:date>
    <dc:language>en</dc:language>
  </item>

  <item>
    <title>An exception handling revelation</title>
    <link>https://www.spinellis.gr/blog/20240205</link>
    <description>
 I’ve been working with exceptions offered by languages,
such as Java and Python,
for more than 20 years, invariably as their consumer:
catching them when raised by an API and then doing my thing.
For the systems I worked on, exception handling mostly involved
either quitting the program with an error or re-prompting the user
to fix some input.
Consequently, my view of them was as a fancy error handling mechanism:
syntactic sugar and static enforcement for checking a function’s
successful completion.
Recently,
 I refactored 
the error handling in
 Alexandria3k ,
a library and a command-line tool providing efficient relational
query access to diverse publication open data sets.
Through this the full power of exceptions clicked for me.
I suspect that others may share my previously limited appreciation
of exception handling,
so here is a brief description of the refactoring. 
</description>
    <guid isPermaLink="true">https://www.spinellis.gr/blog/20240205</guid> <!-- Hardcoded site here -->
    <dc:creator>Diomidis Spinellis</dc:creator>
    <dc:type>Text</dc:type>
    <dc:title>An exception handling revelation</dc:title> <!-- Hardcoded site here -->
    <dc:identifier>https://www.spinellis.gr/blog/20240205</dc:identifier>
    <dc:date>2024-02-05T15:48:57-00:00</dc:date>
    <dc:language>en</dc:language>
  </item>

  <item>
    <title>Extending the life of TomTom wearables</title>
    <link>https://www.spinellis.gr/blog/20230901</link>
    <description>
 TomTom recently announced
 it would stop operating their supporting infrastructure by the end of September 
following its earlier decision
 to exit the wearables market .
This means that its products, such as sports watches, will become effectively
useless, as they will no longer be able to export their activities and
sync them with tracker sites.
Throwing away an otherwise fine watch only because its maker decided to
shut down its proprietary infrastructure seems like a sad waste.
Here is how you can download the watch’s data and
upload it to  Strava , a popular activity tracker,
using open source software. 
</description>
    <guid isPermaLink="true">https://www.spinellis.gr/blog/20230901</guid> <!-- Hardcoded site here -->
    <dc:creator>Diomidis Spinellis</dc:creator>
    <dc:type>Text</dc:type>
    <dc:title>Extending the life of TomTom wearables</dc:title> <!-- Hardcoded site here -->
    <dc:identifier>https://www.spinellis.gr/blog/20230901</dc:identifier>
    <dc:date>2023-11-03T15:57:39-00:00</dc:date>
    <dc:language>en</dc:language>
  </item>

  </channel>
</rss>
