&lt;?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CONSPICUOUS TECHNOLOGIST</title><link>https://www.conspicuoustechnologist.com/</link><description>Recent posts from CONSPICUOUS TECHNOLOGIST</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://www.conspicuoustechnologist.com/feeds/rss.xml" rel="self" type="application/rss+xml"/><item><title>The DPS Phone Ban: I Was Sure I Was Right</title><link>https://www.conspicuoustechnologist.com/2026/05/dps-phone-ban/</link><pubDate>Tue, 26 May 2026 00:00:00 +0000</pubDate><guid>https://www.conspicuoustechnologist.com/2026/05/dps-phone-ban/</guid><description>&amp;lt;p&amp;gt;&amp;lt;span id=&amp;#34;the-email&amp;#34;&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/p&amp;gt;&amp;#xA;&amp;#xA;&amp;lt;div class=&amp;#34;voice-block voice-noise&amp;#34;&amp;gt;&amp;#xA; &amp;lt;span class=&amp;#34;voice-label&amp;#34;&amp;gt;[ 5th grade email ]&amp;lt;/span&amp;gt;&amp;#xA; &amp;lt;div class=&amp;#34;voice-content&amp;#34;&amp;gt;&amp;#xA; &amp;lt;p&amp;gt;&amp;lt;em&amp;gt;5th Grade Families,&amp;lt;/em&amp;gt;&amp;lt;/p&amp;gt;&amp;#xA;&amp;lt;p&amp;gt;&amp;lt;em&amp;gt;To help us maintain a fully engaged and distraction-free learning environment, we are writing to clarify our policy regarding smartwatches. Recently, we have seen an increase in students using the communication and messaging features on their watches during instructional time.&amp;lt;/em&amp;gt;&amp;lt;/p&amp;gt;&amp;#xA;&amp;lt;p&amp;gt;&amp;lt;em&amp;gt;Starting immediately, all smartwatches and phones must be powered off and kept securely inside students&amp;amp;rsquo; backpacks for the entire school day. If a student is seen using their device, or has it out of their backpack during school hours, the device will be taken to the front office. If this happens, parents will be contacted and required to come to the school to pick it up.&amp;lt;/em&amp;gt;&amp;lt;/p&amp;gt;</description></item><item><title>The Ethics of Autonomous Vehicles: Revisiting a 2020 Paper (Part 2: The Trolley Problem)</title><link>https://www.conspicuoustechnologist.com/2026/05/ethics-autonomous-vehicles-part-2/</link><pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate><guid>https://www.conspicuoustechnologist.com/2026/05/ethics-autonomous-vehicles-part-2/</guid><description>&amp;lt;div class=&amp;#34;voice-block voice-jd303&amp;#34;&amp;gt;&amp;#xA; &amp;lt;span class=&amp;#34;voice-label&amp;#34;&amp;gt;[ jd303 ]&amp;lt;/span&amp;gt;&amp;#xA; &amp;lt;div class=&amp;#34;voice-content&amp;#34;&amp;gt;&amp;#xA; Aaaaand now, the moment you have all been waiting for&amp;amp;hellip; the segment pseudo-philosophers squawk about, the cliché corner of the Autonomous Vehicle debate, yet probably the most complex and important&amp;amp;hellip; &amp;lt;a href=&amp;#34;https://en.wikipedia.org/wiki/Trolley_problem&amp;#34;&amp;gt;THE TROLLEY PROBLEM&amp;lt;/a&amp;gt;!!!&amp;#xA; &amp;lt;/div&amp;gt;&amp;#xA;&amp;lt;/div&amp;gt;&amp;#xA;&amp;#xA;&amp;#xA;&amp;lt;div class=&amp;#34;voice-block voice-signal&amp;#34;&amp;gt;&amp;#xA; &amp;lt;span class=&amp;#34;voice-label&amp;#34;&amp;gt;[ the paper ]&amp;lt;/span&amp;gt;&amp;#xA; &amp;lt;div class=&amp;#34;voice-content&amp;#34;&amp;gt;&amp;#xA; &amp;lt;p&amp;gt;&amp;lt;span id=&amp;#34;trolley-problem&amp;#34;&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/p&amp;gt;&amp;#xA;&amp;lt;h2 id=&amp;#34;the-trolley-problem-and-accident-algorithms&amp;#34;&amp;gt;The Trolley Problem and Accident Algorithms&amp;lt;/h2&amp;gt;&amp;#xA;&amp;lt;p&amp;gt;Many ethical, legal, and liability concerns with autonomous vehicles stem from how accident algorithms solve the trolley problem. Philosopher Philippa Foot, who originally conceived of the trolley problem, describes it as a situation where five men are working on a train track and one man is working on another section of track, with a runaway tram heading toward the five men (&amp;lt;a href=&amp;#34;#ref-foot-1967&amp;#34;&amp;gt;1967&amp;lt;/a&amp;gt;). The train operator or another observer must make a choice to either throw a switch to move the tram to the other track, killing only one person, or take no action and allow the train to kill the five men (&amp;lt;a href=&amp;#34;#ref-foot-1967&amp;#34;&amp;gt;Foot, 1967&amp;lt;/a&amp;gt;). Similar situations can arise with various ethical consequences, with Foot providing examples of a judge framing an innocent man when the guilty party is unknown, preventing rioters from violently attacking a community if they do not see justice for a crime, or a pilot making the choice to crash land a failing aircraft to a less populated area (&amp;lt;a href=&amp;#34;#ref-foot-1967&amp;#34;&amp;gt;1967&amp;lt;/a&amp;gt;). With self-driving cars, there are many potential trolley problems, and accident algorithms will need some type of ethical examination for determining who might live or die.&amp;lt;/p&amp;gt;</description></item><item><title>The Ethics of Autonomous Vehicles: Revisiting a 2020 Paper (Part 1: Legislation, Jobs, and the Mobility Gap)</title><link>https://www.conspicuoustechnologist.com/2026/05/ethics-autonomous-vehicles/</link><pubDate>Tue, 12 May 2026 00:00:00 +0000</pubDate><guid>https://www.conspicuoustechnologist.com/2026/05/ethics-autonomous-vehicles/</guid><description>&amp;lt;div class=&amp;#34;voice-block voice-jd303&amp;#34;&amp;gt;&amp;#xA; &amp;lt;span class=&amp;#34;voice-label&amp;#34;&amp;gt;[ jd303 ]&amp;lt;/span&amp;gt;&amp;#xA; &amp;lt;div class=&amp;#34;voice-content&amp;#34;&amp;gt;&amp;#xA; &amp;lt;p&amp;gt;A few weeks ago I was sitting at a stoplight in my Escape, about eight blocks from my house, and a Waymo rolled up next to me. It took me a second to register what I was looking at. The spinning sensor array on top is the tell. I told the kids to look. They looked. I mentioned there was nobody inside. They said &amp;amp;ldquo;cool,&amp;amp;rdquo; asked a couple questions, and by the time we got home it was already yesterday&amp;amp;rsquo;s news.&amp;lt;/p&amp;gt;</description></item><item><title>Raising Hackers: Meet pixie_technologist</title><link>https://www.conspicuoustechnologist.com/2026/05/raising-hackers-pixie-technologist/</link><pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate><guid>https://www.conspicuoustechnologist.com/2026/05/raising-hackers-pixie-technologist/</guid><description>&amp;lt;div class=&amp;#34;voice-block voice-jd303&amp;#34;&amp;gt;&amp;#xA; &amp;lt;span class=&amp;#34;voice-label&amp;#34;&amp;gt;[ jd303 ]&amp;lt;/span&amp;gt;&amp;#xA; &amp;lt;div class=&amp;#34;voice-content&amp;#34;&amp;gt;&amp;#xA; &amp;lt;p&amp;gt;This is the first post in a series called &amp;lt;strong&amp;gt;Raising Hackers&amp;lt;/strong&amp;gt;, written by a 90s hacker turned professional who understands both the genuinely impressive things technology makes possible and the ways it&amp;amp;rsquo;ll work against you if you&amp;amp;rsquo;re not paying attention.&amp;lt;/p&amp;gt;&amp;#xA;&amp;lt;p&amp;gt;Our family&amp;amp;rsquo;s parenting style is not &amp;amp;ldquo;here&amp;amp;rsquo;s a YouTube playlist, don&amp;amp;rsquo;t bug me, I&amp;amp;rsquo;m working.&amp;amp;rdquo; Far from it. We are not iPad parents. We&amp;amp;rsquo;d rather our kids understand: here&amp;amp;rsquo;s what this thing is, here&amp;amp;rsquo;s how to use it, here&amp;amp;rsquo;s what the companies that make it want from you (money), and here&amp;amp;rsquo;s how to protect yourself. A real example of this is that most kid stars on YouTube are &amp;lt;em&amp;gt;&amp;lt;strong&amp;gt;not real&amp;lt;/strong&amp;gt;&amp;lt;/em&amp;gt; (not the way they appear, anyway). We show that with behind-the-scenes research with them.&amp;lt;/p&amp;gt;</description></item><item><title>Getting on Google</title><link>https://www.conspicuoustechnologist.com/2026/05/google-search-console/</link><pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate><guid>https://www.conspicuoustechnologist.com/2026/05/google-search-console/</guid><description>&amp;lt;div class=&amp;#34;voice-block voice-jd303&amp;#34;&amp;gt;&amp;#xA; &amp;lt;span class=&amp;#34;voice-label&amp;#34;&amp;gt;[ jd303 ]&amp;lt;/span&amp;gt;&amp;#xA; &amp;lt;div class=&amp;#34;voice-content&amp;#34;&amp;gt;&amp;#xA; Okay, now that the site is up, I&amp;amp;rsquo;ve got some posts scheduled, why is there low traffic? Oh, nobody knows about it. Time to fix that. The first step is getting it onto Google. Is this something you may have also forgotten to do for YOUR site?&amp;#xA; &amp;lt;/div&amp;gt;&amp;#xA;&amp;lt;/div&amp;gt;&amp;#xA;&amp;#xA;&amp;lt;div class=&amp;#34;voice-block voice-claude&amp;#34;&amp;gt;&amp;#xA; &amp;lt;span class=&amp;#34;voice-label&amp;#34;&amp;gt;[ claude ]&amp;lt;/span&amp;gt;&amp;#xA; &amp;lt;div class=&amp;#34;voice-content&amp;#34;&amp;gt;&amp;#xA; &amp;lt;p&amp;gt;&amp;lt;strong&amp;gt;What you need:&amp;lt;/strong&amp;gt;&amp;lt;/p&amp;gt;&amp;#xA;&amp;lt;ul&amp;gt;&amp;#xA;&amp;lt;li&amp;gt;Access to your domain&amp;amp;rsquo;s DNS panel (DreamHost in this case)&amp;lt;/li&amp;gt;&amp;#xA;&amp;lt;li&amp;gt;A Google account&amp;lt;/li&amp;gt;&amp;#xA;&amp;lt;/ul&amp;gt;&amp;#xA;&amp;lt;p&amp;gt;&amp;lt;strong&amp;gt;Step 1: Add your property in Search Console&amp;lt;/strong&amp;gt;&amp;lt;/p&amp;gt;</description></item><item><title>Oblique Strategies: Building the Card Deck That Unblocks You</title><link>https://www.conspicuoustechnologist.com/2026/04/oblique-strategies/</link><pubDate>Tue, 28 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.conspicuoustechnologist.com/2026/04/oblique-strategies/</guid><description>&amp;lt;div class=&amp;#34;voice-block voice-jd303&amp;#34;&amp;gt;&amp;#xA; &amp;lt;span class=&amp;#34;voice-label&amp;#34;&amp;gt;[ jd303 ]&amp;lt;/span&amp;gt;&amp;#xA; &amp;lt;div class=&amp;#34;voice-content&amp;#34;&amp;gt;&amp;#xA; &amp;lt;p&amp;gt;Brian Eno and Peter Schmidt published a card deck in 1975 called Oblique Strategies. Each card has a single action on it - sometimes a question, sometimes a directive, sometimes something that sounds like an esoteric fortune cookie.&amp;lt;/p&amp;gt;&amp;#xA;&amp;lt;ul&amp;gt;&amp;#xA;&amp;lt;li&amp;gt;&amp;amp;ldquo;Ghost echoes&amp;amp;rdquo;&amp;lt;/li&amp;gt;&amp;#xA;&amp;lt;li&amp;gt;&amp;amp;ldquo;Bridges -build -burn&amp;amp;rdquo;&amp;lt;/li&amp;gt;&amp;#xA;&amp;lt;li&amp;gt;&amp;amp;ldquo;Give way to your worst impulse&amp;amp;rdquo;&amp;lt;/li&amp;gt;&amp;#xA;&amp;lt;li&amp;gt;&amp;amp;ldquo;Idiot glee (?)&amp;amp;rdquo;&amp;lt;/li&amp;gt;&amp;#xA;&amp;lt;/ul&amp;gt;&amp;#xA;&amp;lt;p&amp;gt;What the hell do these mean? Who knows. They&amp;amp;rsquo;re not instructions so much as interruptions. You&amp;amp;rsquo;re stuck, so you draw a card, and it breaks whatever loop you&amp;amp;rsquo;re in. It&amp;amp;rsquo;s supposed to help you move past your block.&amp;lt;/p&amp;gt;</description></item><item><title>Building a Synth Patch Library with Claude (Part 2: The Generator)</title><link>https://www.conspicuoustechnologist.com/2026/04/synth-patch-generator/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.conspicuoustechnologist.com/2026/04/synth-patch-generator/</guid><description>&amp;lt;div class=&amp;#34;voice-block voice-jd303&amp;#34;&amp;gt;&amp;#xA; &amp;lt;span class=&amp;#34;voice-label&amp;#34;&amp;gt;[ jd303 ]&amp;lt;/span&amp;gt;&amp;#xA; &amp;lt;div class=&amp;#34;voice-content&amp;#34;&amp;gt;&amp;#xA; &amp;lt;p&amp;gt;Part 1 covered getting the actual patch data right: correcting .ins files, cataloguing 2,172 patches across 6 synths, and building a reference library. That part was mostly Claude doing data extraction and reconciliation work.&amp;lt;/p&amp;gt;&amp;#xA;&amp;lt;p&amp;gt;Once the library existed, the next problem was obvious: browsing a markdown file is not a workflow. I wanted something that could generate a starting patch combination for a track based on feel, let me pick which synth covers which role, and export directly into Reaper. So that&amp;amp;rsquo;s what we built.&amp;lt;/p&amp;gt;</description></item><item><title>Building a Synth Patch Library with Claude (Part 1: The Library)</title><link>https://www.conspicuoustechnologist.com/2026/04/synth-patch-library/</link><pubDate>Sat, 25 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.conspicuoustechnologist.com/2026/04/synth-patch-library/</guid><description>&amp;lt;div class=&amp;#34;voice-block voice-jd303&amp;#34;&amp;gt;&amp;#xA; &amp;lt;span class=&amp;#34;voice-label&amp;#34;&amp;gt;[ jd303 ]&amp;lt;/span&amp;gt;&amp;#xA; &amp;lt;div class=&amp;#34;voice-content&amp;#34;&amp;gt;&amp;#xA; &amp;lt;p&amp;gt;I have six hardware synthesizers. Each one has its own patch library, its own quirks, its own way of organizing sounds. Some of them have printed manuals. Some have handwritten notes taped to the wall. Some have .ins files that are supposed to tell my DAW what patches exist and where, except those files were wrong. Like, completely wrong.&amp;lt;/p&amp;gt;&amp;#xA;&amp;lt;p&amp;gt;The practical problem is this: when I sit down to write a track, I don&amp;amp;rsquo;t want to dig through menus on six different pieces of hardware trying to remember where I saved that acid bass patch or which synth has the pad I&amp;amp;rsquo;m thinking of. I wanted a way to browse across everything, filter by feel, and get to work. That didn&amp;amp;rsquo;t exist, so I built it.&amp;lt;/p&amp;gt;</description></item><item><title>Bootstrapping This Site</title><link>https://www.conspicuoustechnologist.com/2026/04/bootstrapping-this-site/</link><pubDate>Fri, 24 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.conspicuoustechnologist.com/2026/04/bootstrapping-this-site/</guid><description>&amp;lt;div class=&amp;#34;voice-block voice-jd303&amp;#34;&amp;gt;&amp;#xA; &amp;lt;span class=&amp;#34;voice-label&amp;#34;&amp;gt;[ jd303 ]&amp;lt;/span&amp;gt;&amp;#xA; &amp;lt;div class=&amp;#34;voice-content&amp;#34;&amp;gt;&amp;#xA; &amp;lt;p&amp;gt;I&amp;amp;rsquo;ve been meaning to put something up at this domain for a while. Not a blog in the &amp;amp;ldquo;please subscribe and smash that like button&amp;amp;rdquo; sense. Just a place to write about stuff I&amp;amp;rsquo;m actually doing. Tech, music, tools, the occasional rant. The usual.&amp;lt;/p&amp;gt;&amp;#xA;&amp;lt;p&amp;gt;The question was always what to build it on. The obvious answer is WordPress because it&amp;amp;rsquo;s the obvious answer, and that&amp;amp;rsquo;s exactly why I didn&amp;amp;rsquo;t want it. I already manage too much infrastructure at work. I&amp;amp;rsquo;m not spending my free time chasing plugin updates and PHP vulnerabilities for a personal site. Ghost was the next candidate, cleaner than WordPress, decent API, but it&amp;amp;rsquo;s still a server you have to babysit. I wanted something I could &amp;lt;code&amp;gt;git push&amp;lt;/code&amp;gt; and walk away from.&amp;lt;/p&amp;gt;</description></item></channel></rss>