<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Powershell on Tom Burkert</title><link>https://blog.burkert.me/tags/powershell/</link><description>Recent content in Powershell on Tom Burkert</description><image><title>Tom Burkert</title><url>https://blog.burkert.me/assets/</url><link>https://blog.burkert.me/assets/</link></image><generator>Hugo -- 0.148.0</generator><language>en-us</language><lastBuildDate>Sun, 20 Apr 2025 00:23:12 +0200</lastBuildDate><atom:link href="https://blog.burkert.me/tags/powershell/index.xml" rel="self" type="application/rss+xml"/><item><title>LLMs: Are You Holding It Wrong?</title><link>https://blog.burkert.me/posts/llms-are-you-holding-it-wrong/</link><pubDate>Sun, 20 Apr 2025 00:23:12 +0200</pubDate><guid>https://blog.burkert.me/posts/llms-are-you-holding-it-wrong/</guid><description>&lt;p>Many moons ago (in fact long ago so that contemporary sources are beginning to be difficult to find), iPhone users were told they&amp;rsquo;re &lt;a href="https://edition.cnn.com/2010/TECH/mobile/06/25/iphone.problems.response/index.html" target="_blank" rel="noopener">holding their phones wrong&lt;/a>. This was one of the more memeworthy communication blunders of Apple and something we&amp;rsquo;re unlikely to see from them, but the reason I mention it here is that asking ourselves whether we&amp;rsquo;re holding the thing wrong is actually a good strategy for exploring novel use cases.&lt;/p></description><content:encoded><![CDATA[<p>Many moons ago (in fact long ago so that contemporary sources are beginning to be difficult to find), iPhone users were told they&rsquo;re <a href="https://edition.cnn.com/2010/TECH/mobile/06/25/iphone.problems.response/index.html" target="_blank" rel="noopener">holding their phones wrong</a>. This was one of the more memeworthy communication blunders of Apple and something we&rsquo;re unlikely to see from them, but the reason I mention it here is that asking ourselves whether we&rsquo;re holding the thing wrong is actually a good strategy for exploring novel use cases.</p>
<p>Take LLMs: if humans can do something, or least are attempting to do something, chances are people tried doing it with an LLM, and at least some of those would claim that it does the job just as well as a human (insert many asterisks and caveats in small print if they have at least some integrity). I will not go into debating whether LLMs can replace programmers (or other jobs), or when that&rsquo;s going to happen; many smarter people than myself have done so. I personally use Cursor (one of the fancy AI-first IDEs) at work and have found it to be excellent for <em>certain types of tasks</em>, especially of the exploratory or quick&rsquo;n&rsquo;dirty kind – and much less excellent for other types. But I can&rsquo;t shake the impression that we might be holding it wrong.</p>
<p>One of the common and honestly valid complaints that AI skeptics have is that we&rsquo;re replacing and automating the fun parts of people&rsquo;s jobs, and that has been the focus of the discourse for usage of AI in programming too: the shift from writing code to reviewing AI-generated code is happening quite fast in some industries. Only time will tell what the consequences of this shift are, because no shift of such magnitude happens without unforeseen side effects. But where I find LLMs to be really underappreciated is small-scale automation of everyday tasks, even outside of typically programming contexts.</p>
<p>Here&rsquo;s what I mean: Just a few days ago, I was putting together a few slides for a presentation - one of the really big shared decks for a full-day workshop and with multiple presenters. The file was 499MB. <em>Half. A. Gig</em>. I did not want to make things unnecessarily worse, so I pledged to downsize any stock photography I insert. And this is where the LLMs come in: I knew I could fire up GIMP or some other image editing software, edit the image in a few clicks, save it and be done with it. But this approach does not scale well and I knew I wanted a slightly more sophisticated solution.</p>
<p>Now this very simple problem has a million different solutions, from finding a dedicated software to do this in bulk all the way to writing a Python or Powershell script myself. The problem is I did not have time to fiddle around with this, and even if I did, the ROI was unclear: resizing 5-10 images manually can definitely be done faster than writing such a script, even if you&rsquo;ve done something similar before. In a weird twist, the simplest problems become the most unlikely to automate since they solve just small annoyances, and coming up with a proper solution is not worth the time - or so it seems.</p>
<p>Enter LLMs. For all their issues with understanding larger codebases, using deprecated functions or methods, writing subpar code or just simply not being able to help you with more complex or rarer issues, they excel at small, contained and common problems. <code>Write a Powershell script that takes the latest .jpg or .png image in my Downloads folder, resizes its larger side to 1920 pixels and saves it with a _resized suffix</code> is all I needed to feed to an LLM to solve the issue, and you can bet that it was faster than resizing 5 of the images manually. It also basically does not matter which LLM you feed this into, they can all deal with this type of scripting without a hiccup. (You should always check the code, though: even though an rm -rf / situation is unlikely, you still don&rsquo;t want any surprises.)</p>
<p>This unlocked something in my brain. I started looking for small, repetitive tasks that previously had no ROI, but become very viable with one-shotting the solution with an LLM. Your mileage may vary, but I am finding them everywhere I look.  I realized <em>I was holding it wrong</em>. I should have utilized the LLM to automate the stupid, boring, manual stuff, because the bar for whether it&rsquo;s worth my time automating it is so, so low nowadays. And the best thing about it? I don&rsquo;t have to consider whether it has any impact on my programming foundations, because this is code that I would have never written. If anything, reading it taught me at least a little bit where otherwise I&rsquo;d have done something manually in a piece of software.</p>
<p>I guarantee you that if you work on a computer, then you&rsquo;re doing something repeatedly, and there are good chances you could automate at least parts of it with little effort using an LLM. Don&rsquo;t hold it wrong!</p>
]]></content:encoded></item></channel></rss>