<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on nsf.name</title><link>https://nsf.name/blog/</link><description>Recent content in Blog on nsf.name</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright © 2026, Nathaniel Flores.</copyright><lastBuildDate>Tue, 24 Mar 2026 16:11:18 -0700</lastBuildDate><atom:link href="https://nsf.name/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Raise the Ceiling, Beware the Floor</title><link>https://nsf.name/blog/raise-the-ceiling-beware-the-floor/</link><pubDate>Tue, 24 Mar 2026 16:11:18 -0700</pubDate><guid>https://nsf.name/blog/raise-the-ceiling-beware-the-floor/</guid><description>&lt;p&gt;During March of 2026, the Williams Record was inundated with a flurry of vitriolic, near-identical op-eds covering the topic of AI in the classroom and our society. I did not feel I had anything new to add to the AI debate, but rather I saw it as a symptom of a much broader, older dilemma that has plagued pedagogy for decades: the debate about how much we should allow automation to replace our learning. So I wrote an article about it and published it to the Williams Record, which is what follows below.&lt;/p&gt;</description></item><item><title>Rewriting WSO Mobile in Swift</title><link>https://nsf.name/blog/rewriting-wso-mobile-in-swift/</link><pubDate>Mon, 23 Mar 2026 22:59:16 -0500</pubDate><guid>https://nsf.name/blog/rewriting-wso-mobile-in-swift/</guid><description>&lt;p&gt;At Williams College, most student technological services run through an organization called WSO&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;, for common tasks like checking the course calendar, dining hall menus, rating professors, trading textbooks, and more. Since the college doesn&amp;rsquo;t provide its own app, that means our app is the standard app for the ~2,000 students who are active students.&lt;/p&gt;
&lt;p&gt;Around December of 2025, I began to realize that we should aspire to do better than our current trainwreck of an app. The last time that WSO&amp;rsquo;s aging mobile app was rewritten before the rewrite that I am about to discuss here was all the way back in &lt;em&gt;2016&lt;/em&gt;, meaning the current mobile app was made of nearly &lt;em&gt;a decade&lt;/em&gt; of unmaintained trash. I can&amp;rsquo;t even begin to explain how bad this actually was&lt;sup id="fnref:2"&gt;&lt;a href="#fn:2" class="footnote-ref" role="doc-noteref"&gt;2&lt;/a&gt;&lt;/sup&gt;:&lt;/p&gt;</description></item><item><title>Williams Record: WSO Mobile</title><link>https://nsf.name/blog/williams-record-wso-mobile/</link><pubDate>Wed, 11 Feb 2026 15:17:01 -0700</pubDate><guid>https://nsf.name/blog/williams-record-wso-mobile/</guid><description>&lt;p&gt;In the February 11th, 2026 issue of the Williams Record&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;, there was an article about the new version of WSO Mobile, which had &lt;a href="https://nsf.name/blog/rewriting-wso-mobile-in-swift"&gt;an interesting development cycle&lt;/a&gt;. The Williams Record interviewed me about this and published an article about it; I am archiving it here verbatim for historical purposes (in case the original site goes down).&lt;/p&gt;
&lt;hr&gt;
&lt;figure class="inline-image"&gt;&lt;picture&gt;
 &lt;source srcset="https://nsf.name/images/wso-app-graphic_hu_3c2c8668dce2afae.webp" type="image/webp"&gt;
 &lt;img src="https://nsf.name/images/wso-app-graphic_hu_b66d1ddb50a399c8.png"
 alt="Melania Espinal&amp;#39;s drawing of the WSO Mobile app"
 width="369"
 height="400"
 loading="lazy"&gt;
 &lt;/picture&gt;&lt;figcaption&gt;Melania Espinal/&lt;em&gt;The Williams Record&lt;/em&gt;&lt;/figcaption&gt;&lt;/figure&gt;

&lt;p&gt;A new version of the Williams Students Online (WSO) mobile app was released for all iOS devices on Jan. 26. According to an email from President of WSO Nathaniel Flores ’27, the release marked the first time the app has been updated in six years.&lt;/p&gt;</description></item><item><title>The WSO Server Migration, Part 2</title><link>https://nsf.name/blog/the-wso-server-migration-part-2/</link><pubDate>Sun, 01 Feb 2026 23:41:25 -0500</pubDate><guid>https://nsf.name/blog/the-wso-server-migration-part-2/</guid><description>&lt;h1 id="previously-on-wso"&gt;Previously on WSO&amp;hellip;&lt;/h1&gt;
&lt;p&gt;The big challenge last time that kept me from finally moving everything over to the new server was LISTSERV. This ancient piece of email software dates back to the Paleolithic&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;, and is a maintenance nightmare precisely because it&amp;rsquo;s annoying to get data out of.&lt;/p&gt;
&lt;p&gt;Adding to this burden was cPanel, another nasty fossil that needed to be relegated to the past. Unfortunately cPanel also had all of the configuration for &lt;code&gt;exim&lt;/code&gt; and LISTSERV in it, so the big task would be figuring out how to extract it from the running server in a way that is safe, and then reinstalling as much of the mail archives and list data as possible onto the new server.&lt;/p&gt;</description></item><item><title>The WSO Server Migration, Part 1</title><link>https://nsf.name/blog/the-wso-server-migration-part-1/</link><pubDate>Sun, 12 Oct 2025 19:00:00 +0000</pubDate><guid>https://nsf.name/blog/the-wso-server-migration-part-1/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;/h1&gt;
&lt;p&gt;First, a bit of context: &lt;a href="https://wso.williams.edu"&gt;WSO&lt;/a&gt;, officially &lt;em&gt;Williams Students Online&lt;/em&gt;, is a project started in 1995 at Williams College to provide student online services that the college was either unwilling or unable to provide for the community (such as FacTrak, an early predecessor to services like &amp;ldquo;Rate My Professor&amp;rdquo;). Amazingly, it had been hosted on nearly the same hardware for about a decade now, and has mutated to the point where it is hardly recognizable as a classic LAMP (Linux, Apache, MySQL, PHP):&lt;/p&gt;</description></item><item><title>Daily Japanese Study: 2025</title><link>https://nsf.name/blog/daily-japanese-study-2025/</link><pubDate>Sat, 11 Oct 2025 19:00:00 +0000</pubDate><guid>https://nsf.name/blog/daily-japanese-study-2025/</guid><description>&lt;h1 id="background"&gt;Background&lt;/h1&gt;
&lt;p&gt;Sometimes an accidental decision has interesting second-order consequences that you really don&amp;rsquo;t see coming. One of them was being dropped from my intended class during my first-year fall and having to take JAPN 101 instead. Unexpectedly, I found that I quite liked the challenge, and soon I found myself increasingly invested in something I had never originally intended doing:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fall of 2023: JAPN 101, starting to quite like the grammar challenges, investing increasingly more time into the language.&lt;/li&gt;
&lt;li&gt;Winter of 2023/2024: JAPN 99 (Winter Study) course, applying to Japanese summer intensive programs, getting into &lt;a href="https://www.kcjs.jp"&gt;KCJS&lt;/a&gt;!&lt;/li&gt;
&lt;li&gt;Spring of 2024: APN 102, begin assembling my own Anki deck (&lt;a href="https://en.wikipedia.org/wiki/Zipf%27s_law"&gt;Zipf&amp;rsquo;s Law&lt;/a&gt; sorted collection of coursework vocabulary), finishing Genki 1 and 2 in my free time to be ready for the summer.&lt;/li&gt;
&lt;li&gt;Summer of 2024: Complete &lt;a href="https://www.kcjs.jp"&gt;KCJS&lt;/a&gt;, which is effectively equivalent to completing JAPN 201-202 at my school.&lt;/li&gt;
&lt;li&gt;Fall of 2024: Then JAPN 301, which is the single hardest humanities course I have ever taken.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Then something shifted in my thinking around the winter of 2024. By that point, Japanese study was so engrossing that I had to make the call to prioritize what mattered most: my Geosciences studies. What drove me to make this choice was because I realized that a class I really wanted to take in Geosciences conflicted with the time offerings for Japanese, and that taking both would effectively be an overwhelming workload that would prevent success in either course.&lt;/p&gt;</description></item><item><title>Williams Record: WSO Interview</title><link>https://nsf.name/blog/williams-record-wso-interview/</link><pubDate>Wed, 17 Sep 2025 15:45:29 -0700</pubDate><guid>https://nsf.name/blog/williams-record-wso-interview/</guid><description>&lt;p&gt;In the September 17th, 2025 issue of the Williams Record&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;, there was an article about the changes that had been going on to WSO, as at the time that I had joined the board officially it was somewhat in a state of disrepair and in need of some fixes. I was interviewed and I want to preserve what the Williams Record published about it; I am archiving this interview here verbatim for historical purposes (in case the original site goes down).&lt;/p&gt;</description></item></channel></rss>