devlog/public/posts/index.xml

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Posts on Coding with Andrzej</title>
    <link>http://localhost:1313/posts/</link>
    <description>Recent content in Posts on Coding with Andrzej</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 24 Nov 2024 15:23:50 +0100</lastBuildDate>
    <atom:link href="http://localhost:1313/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Classroom Buzzer App</title>
      <link>http://localhost:1313/posts/buzzer-game/</link>
      <pubDate>Sun, 24 Nov 2024 15:23:50 +0100</pubDate>
      <guid>http://localhost:1313/posts/buzzer-game/</guid>
      <description>&lt;h2 id=&#34;i-started-working-on-a-new-project-today&#34;&gt;I started working on a new project today.&lt;/h2&gt;&#xA;&lt;p&gt;The client is an educational services provider and wants me to develop a tool to facilitate in-person group activities. This tool should:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;provide a platform which students can log into from a mobile device, in a frictionless process that takes seconds&lt;/li&gt;&#xA;&lt;li&gt;allow a teacher to assign groups and pairs in&lt;/li&gt;&#xA;&lt;li&gt;allow the teacher to dynamically reassign groups without repeating combinations&lt;/li&gt;&#xA;&lt;li&gt;implement a simple score-keeping functionality&lt;/li&gt;&#xA;&lt;li&gt;be able to run a &amp;lsquo;buzzer&amp;rsquo; game&lt;/li&gt;&#xA;&lt;li&gt;have a clean, appealing, and user-friendly UI&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;A quick read of this brief should make it clear that what is required here is a server capable of handling multiple, live, two-way connections. The server needs to be able to update the clients whenever the teacher wants to shuffle the groups, and the buzzer game requires that when a student &amp;lsquo;buzzes&amp;rsquo;, state is propagated via the server to all other clients. The solution to this problem is websockets, and a server capable of handling concurrency.&lt;/p&gt;</description>
    </item>
    <item>
      <title>More cache-busting</title>
      <link>http://localhost:1313/posts/cache-busting-2/</link>
      <pubDate>Fri, 15 Nov 2024 22:33:10 +0100</pubDate>
      <guid>http://localhost:1313/posts/cache-busting-2/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Well, that was easy.&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;At the end of &lt;a href=&#34;cache-busting&#34;&gt;my last post&lt;/a&gt;, I had successfully written a script to stop stale CSS from getting stuck in the browser cache. It was a rough-and-ready solution &amp;mdash; mine usually are &amp;mdash; but it did the job. The one optimization I wanted to make was to ensure that the cache gets busted &lt;em&gt;only&lt;/em&gt; when there is fresh CSS, as opposed to on every build. I had expected to get a nice long blog post out of this, but it turns out to be a very easy job.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Invalidating the browser cache</title>
      <link>http://localhost:1313/posts/cache-busting/</link>
      <pubDate>Thu, 14 Nov 2024 14:24:21 +0100</pubDate>
      <guid>http://localhost:1313/posts/cache-busting/</guid>
      <description>&lt;p&gt;&lt;strong&gt;I had a bit of an issue with my &lt;a href=&#34;https://demos.ajstepien.xyz&#34;&gt;website&lt;/a&gt; recently.&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;I pushed some changes incorporating images for the first time (I know &amp;ndash; very swish, very modern), and everything seemed to be working just fine, but when I loaded the production site in Firefox&amp;hellip; the images were not styled. Stranger still, they &lt;em&gt;were&lt;/em&gt; styled when I loaded the same page in Chrome.&lt;/p&gt;&#xA;&lt;p&gt;The experienced computer touchers amongst you will be saying &amp;ldquo;this is obviously a cache problem&amp;rdquo;, and you&amp;rsquo;re right, it is obviously a cache problem. Pressing &lt;code&gt;CTR + SHIFT + R&lt;/code&gt; (which forces Firefox to clear the cache and do a full reload) proved this thesis, and solved the immediate problem for me, on my machine. But what about other people&amp;rsquo;s machines? &lt;strong&gt;I needed to cache-bust.&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Permissions strike again</title>
      <link>http://localhost:1313/posts/permissions-strike-again/</link>
      <pubDate>Wed, 13 Nov 2024 11:53:13 +0100</pubDate>
      <guid>http://localhost:1313/posts/permissions-strike-again/</guid>
      <description>&lt;p&gt;Configuring Apache really isn&amp;rsquo;t rocket science. There are a wealth of great tutorials online, the documentation is very well documented, and the defaults work more or less out of the box. But it&amp;rsquo;s one of those jobs that I do just infrequently enough that I always forget things in the interim, and end up making the same old mistakes.&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;&lt;strong&gt;And it almost always has to do with permissions.&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;So, I&amp;rsquo;m writing this post both as a means of christening this devlog (&lt;a href=&#34;https://demos.ajstepien.xyz&#34;&gt;Hi! I&amp;rsquo;m Andrzej! Hire me!&lt;/a&gt;) and also as a reminder to myself that &lt;em&gt;the home folder is not executable by default.&lt;/em&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>