Gluing Polypropylene Corrugated Plastic (Coroplast)

Late at night, when I should be doing work or, better yet, sleeping, ideas spring to mind.  I’ve created a few small projects from big sheets of coroplast or polypropylene corrugated plastic.  This is the kind of material you see in use for yard signs.  They are big, cheap, sturdy (as long as you’re not bending it with the grain), and lightweight.  They can be bent or cut easily.  However, since it is polypropylene, it is fairly resistant to most glues, adhesives, and paints.

Duct tape and hot glue work well, but have their downsides.  The duct tape can be unsightly and not very good for “laminating” several layers together.  Hot glue works well for laminating layers, but it cools so fast that it’s hard to glue big sheets together.

Anyhow, all of this is to say I found a great website by Christine DeMerchant which provides a lot of information and insight on how to glue these materials together.

How to “Unthread” Emails in Thunderbird v115

If you’re just here for the solution (or, you’re actually me, returning some time in the future to fix the problem after perhaps a Thunderbird update), here’s all you need to know:

  1. Click on the icon in the top right that looks like a film strip which displays the “Message list display options” when the mouse hovers over it.
  2. Sort by -> Unthreaded
Just follow these steps, starting with the menu at the top right

Just follow these steps, starting with the menu at the top right

I suppose there are times when threaded email view is useful.  However, when reviewing emails at a glance, it’s incredibly frustrating because your inbox will show you have a new unread email, but you won’t know which thread it’s nested under.

I found numerous “solutions” online for how to unthread Thunderbird emails, but none of them worked for me since the answer wasn’t buried in any of the settings, the hamburger menu didn’t help, and nothing relevant showed up in the help sections or even in searching the settings section.

Of course, right clicking on the columns allowed me to hide the “thread” column, but that didn’t stop emails from actually being threaded.

I spent some time searching for the answer, watching snippets of videos, and finally stumbled across the solution here after seeing multiple people voice the very same frustrations I did, discussing.  Hopefully the above screenshot helps you (or me!) solve this problem in the future.

Heat Transfer Vinyl T-Shirts Without a Craft Cutter (2023)

Saturday, October 21
Zone 2 – Make: Demo Stage
2:30 pm – 3:00 pm
Let’s goooooooooooooooooooo!

Heat Transfer Vinyl T-Shirts (Without a Craft Cutter)
  1. Heat Transfer Vinyl T-Shirts – Without A Vinyl Cutter
  2. Heat Transfer Vinyl T-Shirts – Without A Vinyl Cutter, Part II
  3. Heat Transfer Vinyl T-Shirts Without a Craft Cutter (2023)

Companion Robots and Maker Faire Season!

I’m super excited for Maker Faire Bay Area / Mare Island and Mini Maker Faire Rocklin.1  I’m not just excited to see everything, but to show all the things I’ve been working on for a while now.  It’s also time to pick up all the little dev boards I’ve somehow accumulated and see if I can make anything with them to show off.

  1. Project Boards
    1. Wemos D1 Mini.  A small insanely cheap (~$3?!) WiFi enabled dev board2 , which has 4MB onboard and can run Arduino.  I think it can also run MicroPython, but I haven’t tested this yet.
    2. Wemos 600 Pico.  An even smaller, even cheaper (~$2 when ordered from China) WiFi enabled dev board that runs… MicroPython?  I think??  I’m saying “I think” because I haven’t been able to get it to do anything yet.
      1. Since starting this blog post, I found a guide on installing MicroPython on Wemos boards that seems promising.
        1. Flashing MicroPython on an ESP8266
        2. https://github.com/espressif/esptool/tree/master
        3. Arguing with Python to let me use “esptool.py”
          1. esptool -p COM13 -c esp8266 flash_id
      2. As promising as that series of blog posts looked, I eventually scrapped the Wemos because it was just too much of a pain to get going with MicroPython.  I think I could have made it work, but for $7 I could also just use the Adafruit QtPy I already have.  The advantages of simply uploading code over a USB cable into a virtual drive just can’t be overstated.
    3. Other Boards
      1. I have a bad habit of picking up dev boards.  I’ve got several Adafruit QtPy’s, several Adafruit Trinkets, an Adafruit FX Sound Board, Raspberry Pi Pico (non-WiFi), various Digispark boards, a small handful of ATTiny85’s, and an even weirder assortment of VERY small programmable circuit boards (ISD1806B-COB) designed to go in greeting cards (just 6 seconds), etc.
  2. Companion Robot
    1. Background.
      1. I started this post at least a month ago when I only had a vague idea of what I wanted to make and even fewer skills.  After seeing my kid’s companion robot take shape, I wanted to get in on the action and make my own.  I decided to make a really small companion robot with just some LED’s, piezo, and small microcontroller unit.  I’d taken a stab at making a companion robot a few years ago, but set it aside for a variety of reasons and never went back.
      2. The idea for this new robot would be something a little less ambitious, make more use of NeoPixels than in prior projects3, with a little more interactivity, trying out some CircuitPython, and… let’s be real… more pizzazz!
    2. Idea:  Friendly Cloud/Vapor/Flame
      1. I still really like the copper-toned PLA I’ve been using since it has something of a steampunk flair to it.  I settled on repurposing a small plastic enclosure with a clear dome as the “body” for the robot.  I wanted it to look something like a small entrapped / captive / domesticated4 sentient cloud of vapor or perhaps flame held within a steampunk enclosure.
      2. As a very small, inexpensive board that could run either Arduino or CircuitPython, I decided on the Adafruit QtPy M0.  It could run NeoPixels, there were lots of cool guides on it, plenty of pinouts, and could definitely fit within the confines of my enclosure.
    3. Enclosure:
      1. I started the enclosure by trying to design and 3D print a part to mate with the clear plastic dome.  It took a few tries.

        This slideshow requires JavaScript.

      2. Once I had that, I extended the base so it could hold more electronics.  I could definitely have shoehorned everything into the dome, especially if I took up some of the space inside the dome, but even with an “elevated base” it was still plenty small and could use a battery pack rather than a rechargeable lipo.
      3. Once I had a good design for the enclosure, I tried to make it work with an existing 3xAAA battery pack.  In the process I yanked off the connector and ended up soldering the battery pack leads directly into the circuits.
    4. Internal Electronics
      1. I’m just not a great electrical engineer and am still copy/pasting from various guides, tinkering, changing bits of code, swapping out parts, and using “close enough” resistors.  Wiring up some LEDs or a piezo to a project isn’t very difficult – it’s some of the more fiddly bits.
      2. Piezo Element Speaker
        1. I wanted to use a piezo buzzer/speaker because they’re large and incredibly thin.  They’re not without their downsides.  The crystal wafer is also thin and a little fragile.  The piezo buzzer without additional electronics has the potential to act as a knock sensor and can generate a high voltage spike which can fry a board.  And, without additional electronics, the piezo just isn’t very loud.  There are some libraries for the Arduino that basically double the volume of a piezo by connecting it to two pins and then running each opposite of the other, doubling the voltage difference, but they only work for Arduino chips.5
        2. After searching for various ways to increase the sound of the piezo elements, I settled on trying to use the Adafruit piezo amp.  I bought two – and tried desoldering the terminal blocks.  This completely ruined one.  The other one worked great, but for the modest volume gain it was just too big in an already cramped enclosure.
        3. After searching around, I found some amplifier circuits using a small number of common parts.6
        4. Then I tried building an amplifier circuit using an NPN transistor.  After reviewing the datasheets for my NPN transistors (and PNP transistors), and breadboarding the circuit with resistors, I sketched it a few times, laid it down with copper tape, soldered it in place with SMD resistors, then pulled it off and placed it onto a piece of Kapton tape and put another piece on top – “laminating” it in place.
      3. Capacitive Touch
        1. Buttons are great and all, but with a capacitive touch pad, I could add metallic elements to my robot rather than a much bulkier button.  I bought a few brass upholstery tacks because they looked great – but they just would not accept molten solder.  I ended up cutting the prongs short with wire cutters, wrapping the stub with copper tape, then soldering the wires to the tape.  I’d also added a little piece of heat shrink tubing over the connection to help keep it together.  It’s been working well so far.
      4. LED Animations
        1. As we know from Phillip Burgess‘ incredible “power sipping NeoPixel” guide, we can conserve power and increase the impact of the LED’s by reducing the number of LED’s, keeping max brightness ~20% for a disproportionately large impact, running fewer LED’s at a time, and even running fewer colors at a time.  Between Phillip’s work, Todbot’s guide, and the specialized QtPy NeoPixel guide by Kattni Rembor, I was able to put together a few neat animations.
      5. Piezo Sounds
        1. I had a heck of time getting the piezo buzzer to do anything interesting.  Fortunately, with my kid helped convert the piano music for “Paint It Black” into tones for me.  I haven’t gotten all the note timings right, but I’m working on it!
  3. Future Modifications
    1. More Accessible Enclosure.  Right now the “lid” with a hole for the LED ring just sits on the enclosure with a light friction fit.  One idea is a hinged lid, either with a conventional hinge or perhaps a hidden swivel hinge.  The problem with that, of course, is it requires even more internal space.  Other ideas include a ring on top that screws down, holding the top down and in place.  I’m crap at designing screw threads, so I’ve avoided this.

      Hinged lid for enclosure

      Hinged lid for enclosure

    2. Piezo Knocks.  Perhaps the next version will include some kind of tap / double tap / knock sensors using one or more piezo elements.
    3. Knobs.  There’s not a ton of room inside the enclosure, but by including a gear within a gear, I might be able to rotate part of the case and have it manipulate a potentiometer.

      Offset gear within gear, manipulating an off-center internal potentiometer

      Offset gear within gear, manipulating an off-center internal potentiometer

    4. Motors.  A robot that just flashes lights and makes a few beeps can still be pretty interesting.  However, I have some neat potential features that could be added with just one or two motors.  There are some interesting limitations with the current incarnation of this robot and using a QtPy.  I’ve only got 10 pinouts7 , 1 for NeoPixels, 1 for the piezo, 6 in use for the capacitive touch sensors, leaving 2 for other potential tasks.8  However, space is already tight so one or two micro servos would be a big space commitment.  I’ve seen some really tiny micro servos that might work, but I have no idea where to source them.  One silly idea is a “weapons system” using a spring loaded projectile activated by a very small servo.

      A small spring loaded projectile launcher, actuated by a small servo

      A small spring loaded projectile launcher, actuated by a small servo

    5. Creating Tone Library.  The basic piezo tones are easy enough to play, but including the entire list of tones and the frequencies associated with them seems eat up the poor little QtPy’s memory.  I think compressing them into a library might be the way around this issue.
    6. Playing WAV files.  WAV files are bulky, but that’s the only sound file format a QtPy M0 can play.  However, with the extra 2MB from the SPI chip installed, this shouldn’t be a huge problem.  I used Audacity to mix the sound clip down to mono then to 22 KHz sample rate.  My preliminary tests worked – but it was incredibly quiet.  I haven’t run it through the audio amplifier yet, but I’m planning to.
    7. Sleep / Deep Sleep.  Ever since I swapped out the tiny LiPo for a 3xAAA battery pack, I’ve had a lot more battery life, so adding sleep / deep sleep functions haven’t been a priority.  However, this inclusion just couldn’t hurt.
  4. Other QtPy and CircuitPython Resources
    1. Adafruit’s QtPy CircuitPython PWM resource
    2. TodBot’s CircuitPython tricks
Companion Robots: Building Robot Friends
  1. Cephalopod Robot Friend, the story so far
  2. Cephalopod Robot Friend Progress
  3. CuttleBot Body and OpenSCAD Design Tips
  4. An Assembled CuttleBot Body
  5. Building the Monocle Top Hat Cat for #MicrobitVirtualConcert
  6. Companion Robots and Maker Faire Season!
  1. I just got a notice they’re no longer a “Mini”! []
  2. pinouts for my future reference []
  3. LED goggles and a Marvel Universe inspired set of “Infinity Knuckles” []
  4. OMG dome-sticated?! []
  5. This is just my very basic understanding of how it works.  I’m entirely positive this is far too simplified. []
  6. And one very long article about using a lot of parts []
  7. 12 if you want to count the onboard NeoPixel []
  8. Or 4… []

Beep Boop: Emotions for ED-E

So I’m trying to program emotions for ED-E.

Better ed-e dialogue at Fallout New Vegas - mods and community

In Fallout New Vegas, ED-E doesn’t use regular dialogue, but communicates through beeps. Basically, he gets <(Emotion) + beeping> as his dialogue. Obviously the only way to research his beeping for this project is to replay Fallout New Vegas and talk to everyone’s favorite eyebot. I came up with a list of some of the emotional beeps he has in the game (and some that I just want) to start programming into him. I have ideas for what I want him to sound like, but I just need to find the right pitches and durations.

By this I mean I am sitting in my room and saying “beep beep” to myself at different pitches in sync with a program I wrote.

Yesterday my dad was checking in on me and how my programming was going and asked how I was doing. I replied, approximately, “bleurrrrghhhhh.”
I was having trouble programming the emotional beeps because I have very specific ideas for what ED-E should sound like and no way to get that into a computer. I’m a huge music nerd, but I unfortunately don’t have perfect pitch or some superhuman ability like that to use to get ED-E to sound exactly like I want him to.1 Dad suggested using a loop with an array going up every time, which made everything so. Much. Easier.
This plays frequencies starting at 100hz and going up by 10hz every time. I started with 100hz but going up by 50hz every time, but I liked the specificity of 10hz. Once I get in the ballpark of where I want to be, I can then just run the program and correct the pitches if need be.
If you read my last post, specifically the spoiler section, you will know why I started with a shy beep. If you didn’t read my last post, go do that! If you didn’t read the spoiler section, that’s fine. What you really need to know is that I want ED-E to make noises.
I’ll admit, this took a while to get right. Not playing the tones or even figuring out what pitches they were or how long they should play for. No, getting the tones to play was easy. Getting them to stop… was much harder.
ED-E was shyly screaming at me on repeat for at least 10 minutes while I was slowly losing my mind and trying to make him shut up.
I turned to ChatGPT to help me fix this, but it was utterly unhelpful and I ended up fixing the problem myself by deleting a bunch of the garbage it generated. Now the problem was that I had to continually upload the code to make the ShyBeep function run again. I was happy that it wasn’t looping anymore, but I wanted to fine tune the beeps and making it upload again and again was a pain. That’s why I decided to make it run when a button is pressed.2
It took a little while to make it run when a button was pressed, but then it would only run once and never again, even if the button was pressed. I finally realized that this was happening because runOnce was set to false, and fixed that.
Now that I have this framework, it has been much easier to program more beeps. Now I have a sad beep, and I’m going to start working on a happy beep because I have had just about enough of ED-E’s negativity.3
  1. I almost decided to use the definitions of pitch from my Rickroll code so I could just ask the computer to start at middle C and go down or say I want the pitch to be a half note in 3/4 time. I then realized I was making this WAY more complicated than it needed to be and just used seconds and hz like a normal-ish person []
  2. I seriously love Circuit Playgrounds. They have everything. []
  3. Just kidding ED-E, I love you []

ED-E Project: Origins

Hi, I’m DexterStarfighter, offspring of MakerBlock.1 I am a maker and artist with possibly too many interests that include drawing, writing, cats, theatre, video games, horror podcasts, folklore, coding, Jenga, history, triangles, succulents, and reading literally anything. I have been going to MakerFaire for basically my entire life and it has always been something I look forward to for the whole year. As soon as Dad told me MakerFaire was coming back, I knew I had to make something super cool for the occasion. This brings me to my latest project, a companion robot.

First, some background. My favorite game is part of the Fallout series (New Vegas, if you were wondering). I started the Fallout series because my dad played them when the first Fallout came out and I wanted to be able to share a cool game with him. I started Fallout 1 and loved it, then played Fallout 2 and 3. Over the summer, Epic Games released Fallout New Vegas with all DLCs for free and of course, I played the crap out of that.23

In Fallout New Vegas, there are various companions you can take with you on your journey through the Wasteland. There are human companions of course (and ghoul and nightkin), but you can also take with you one nonhuman companion. At first I was super disappointed that I couldn’t find Dogmeat. I don’t actually like being around dogs in real life, but I got Dogmeat in Fallout 1 and somehow I have become very attached. (I do not even want to think about how many times I have reloaded a save to keep that little jerk alive.) I quickly got over my disappointment though, because there is a statue of a dinosaur and now I’m disappointed that you can’t have a dinosaur robot companion. Anyway, in my travels through the Mojave, I found two interesting nonhuman companions. The first one I found was this little eye bot named ED-E. I play as a charismatic nerd (high INT and CHA with good repair, speech, barter and science) so I was able to fix him up. ED-E was still only able to beep in ways I couldn’t understand and when I brought him to where I was supposed to for his quest, there was some sort of glitch and I couldn’t interact with the lady for the quest. ED-E seemed kind of lame to me then, so I took him back to the place I found him and left. I later ran into a dog named Rex who I had to take care of for an Elvis impersonator (no, really) and found he was a pretty good companion.

Flash forward to the endgame. I had met a cowboy robot, climbed a dinosaur statue, resurrected a B-29, fought a soldier for a dog’s brain, charmed a scientist, accidentally sided with the mafia, cleaned out an entire casino, assassinated a 261-year-old man, had my vital organs removed, stolen 27 bars of gold, befriended a man wrapped in toilet paper, and was well on my way to conquering New Vegas for myself. I had only one more thing to check off my list: walking the Courier’s Mile. Don’t worry, I won’t spoil the Lonesome Road quest for you- I’ll just tell you that I met ED-E again. Somehow, within the first few minutes of interacting with him, I had become so completely charmed by this little robot that I would do literally anything to protect him. I’m not sure what about ED-E made him so endearing to me, but he became my best friend. 

GameBanshee

In 2019, I met Odd_Jayy at MakerFaire. I remember seeing his spider bot and thinking how cool it was. I’ve always liked the idea of a companion bot, but I’ve never actually had a specific idea of what I want out of one. When dad told me that we would be going to MakerFaire again, I immediately thought of an ED-E companion bot.4 Dad loved the idea too and gave me lots of good tips on how to get started. I have a tendency to get lost in the details, so he helped me focus on the big picture and the first steps I could take to achieving my goals.

I have a lot of ideas about what I want ED-E to do eventually, but I’m a complete beginner at Arduino programming. Knowing this, Dad suggested starting small. First, turn on one light. Then multiple lights. Then make them flash. Then make them change colors. Then add beeps. Stuff like that. I was like “cool, cool” and immediately programmed ED-E to beep the entirety of Never Gonna Give You Up instead of doing literally anything sensible.

I regret nothing. It was frustrating at first because I was super out of my depth. I used Chlorondria’s arrangement of Never Gonna Give You Up and used ChatGPT to help me learn how the code works. ChatGPT was super helpful because I could get feedback on why my code wasn’t working. The sense of accomplishment when I finally recognized the tune made all the frustration so incredibly worth it.

After my self-indulgent first project for ED-E, I moved on to taking Dad’s suggestions. Sort of. I’m a teenager, and therefore I am legally obliged not to listen to any authority figures, real or perceived. I made ED-E flash some rainbow lights. I started with just red lights and it took a while to make the code work, but once I made it work, I just changed the color brightnesses. Fun fact: my ED-E bot now actually glows two shades of blue in his rainbow light show pattern. For some reason I decided RGB stood for Red Yellow Blue and messed up with the color values when I was trying to make green and accidentally made a light blue. The light blue actually looked pretty cool, so I decided to keep it.

Today, I worked more on5 ED-E’s… musical function. I’m going to warn you right now: there will be spoilers for MakerFaire below! I intend to take ED-E to MakerFaire with me, and if you meet him, there will be some fun surprises in store for you. Not if you read the spoilers, though. MakerFaire is a big place and I don’t expect everyone who visits this page to run into me at the Faire, so I’ll include some stuff about the surprises below. 

***SPOILERS START***

 

If you’re still here, I assume you want to read this. One of my favorite things about ED-E in Fallout are the little conversations you can have with him. I want to be able to have a few little “conversations” with my companion bot, kind of like in the game. I’m going to have a Pip-Boy with various buttons to run functions for ED-E, but one of the first conversations I thought of had to do with his musical function. This was my idea:

 

Me: Hey, ED-E. Do you wanna sing them your favorite song?

ED-E: [Shy beeping]

Me: Aw, are you shy?

ED-E: [Shy beeping]

Me: Come on, ED-E. We’d all really like to hear you sing!

ED-E: [Questioning beeping]

Me: Yes, of course! Listen, I’ll ask them. Do you want to hear ED-E sing his favorite song?

Other person: Yes!

Me: See, ED-E? 

ED-E: [Pleased beeps, wait, then Rickroll beeps]

 

Obviously, I’m not going to make ED-E understand my words and respond to them. ED-E will be a shoulder mounted bot, so I want to be able to have conversations that trigger based on movement. I’m using a Circuit Playground, so I intend to take full advantage of all the different sensors it has. I programmed ED-E to run his Rickroll function if he senses a significant change in acceleration. I’ll pop my shoulder like I’m giving him a nudge, triggering the function. He waits for 8 seconds to give me time to talk, then plays the Rickroll beeps.

I have to admit, this took a WHILE to get right. It was still incredibly satisfying to see it all come together and go right. I was so excited when it started working! I did a lot of testing to get the sensitivity right because I don’t want it to trigger if I’m just walking around. I’m still fine tuning that part because I bumped the cord earlier and he started Rickrolling me. Then again, maybe ED-E just has a funny sense of humor.

 

***SPOILERS END***

So, what’s next for ED-E? I think the next thing I want to work on is getting his beeps right. I can make him beep music, and that’s great, but I also want to have him beep every so often and have “conversations” with him. I’m going to program some little beep clips for different emotions or situations that I can then mix and match into various conversations. I might also actually listen to Dad for once and work on a light show.

Thanks for reading about my ED-E project! I’ve enjoyed working on him and I’m so excited to share him with other makers. I’ll try to post updates regularly (they shouldn’t be as long as this one since you won’t need all the background next time). Thank you to Odd_Jayy for the inspiration, Chlorondria for the musical arrangement, ChatGPT for the troubleshooting help, Adafruit for making awesome boards, whoever made Fallout New Vegas, MakerBlock for being a great dad and helpful sounding board, and to you for reading this post.

ED-E Companion Bot Project

  1. ED-E Project: Origins
  2. Beep Boop: Emotions for ED-E

  1. I considered saying progeny and descendant of the House of MakerBlock, but offspring sounded the best. Progeny sounded weird and the descendant thing reminded me of Game of Thrones, which I have not read or watched, but I might someday and I don’t want to invite spoilers. []
  2. I love Epic Games. Free games every week? Yes please! Disclaimer: I am not being sponsored by Epic Games, but if I was, that would be awesome. []
  3. New Vegas is best Fallout, you can fight me on this. []
  4. I also considered a Muggy companion bot. I love Muggy and if ED-E turns out well, Muggy might be my next project. []
  5. Lol, moron []

Coding with an LLM Sidekick

I fell down a rabbit hole recently which lead me to think about my experiences in the nascent field of “prompt engineering.”12

As a thought experiment, I was thinking about what I’ve managed to accomplish working with an LLM, the challenges along the way, and perhaps even where I can see the frayed edges of its current limitations.

After several starts and stops trying to hire someone to assist with a website I own, I turned to the idea of getting help from an LLM. 3 4  After all, some of them were touted as being able to actually draft code, right?  Besides, if the first step in even hiring a developer is just being able to describe what you need, and the first step of getting an LLM to generate some code is defining what I need, then…

There's no way this is going to work, right?

There’s no way this is going to work, right?

  1. 1. Task 1:  Pie Chart WordPress Plugin

    1. I started off with a simple and easy to define task.  My original plugin was a quick and dirty bit of code, so if ChatGPT could create a WordPress plugin, there was a chance it could do something simple like this.
    2. My first attempt was a wildly spectacular, but highly educational, failure.  A brief description of the plugin’s function was enough to get a WordPress plugin template file with very little functionality.  Then came the arduous LLM wrangling, my asking it for refinements, it losing track of the conversation, and the endless sincere heartfelt apologies from ChatGPT about forgetting really basic pieces of information along the way.  Some changes were minor, but changing the names of variables, functions, the plugin, switching API’s, forgetting requirements, etc.  It was constant whack-a-mole that spanned nearly 90 pages of text.
    3. My next attempt was more focused.  I created a framework for discussions, provided more context, goals, descriptions of workflow, and resources for examples.  The result was a lot better, with portions of largely functional code.  However, the LLM kept forgetting things, renaming variables, files, directories, etc.
    4. Next I created the directory structure and blank placeholder files, zipped these, and uploaded them as an attachment for the LLM to review – along with a description of the contents and the above additional context.  This was even better than before, but after a certain depth of conversation no amount of reminding could bring the LLM around to the core of the conversation.
    5. My thinking was that after a certain level of conversation, the LLM was not going to be able to synthesize all of nuance of our conversations plus the content of the code drafted.  To get around this I would begin a conversation, make a little progress, then ask it to summarize the project, the current status, and a plan for completion – which was fed into an entirely new conversation.  This way, Conversation N was able to provide a succinct and complete description which Conversation N+1 could use as a jumping off point.  My thinking was that the LLM would be best positioned to create a summary that would be useful to another LLM.
    6. This process of minor “restarts” in the conversation was one of the most successful and powerful techniques I’ve employed to combat LLM hallucinations and forgetfulness.
  2. 2. Task 2:  Blog Post Series Plugin

    1. After rewriting the above pie chart plugin using an LLM, I turned my attention to a slightly more complicated plugin.  The pie chart plugin is really just a single file which turns a shortcode with a little bit of data into a nice looking pie chart.  There’s no options page, no cross post interaction, database queries or anything.  It was really just a test to see if an LLM could really draft a basic piece of working code.
    2. The series plugin is still a reasonably simple piece of code, but it has several additional feature which require a settings page, saving settings, custom database queries, and organizing information across multiple pages.  It’s also one of the most used plugins on this website.
    3. I figured I would try feeding the LLM a description of my plugin, all the code in a directory structure, and then my initial “base” prompt which explains our roles, needs, resources, and scaffolding for a discussion.  I asked the LLM to summarize the function and features of the plugin, which it did quite nicely.  I added a few additional features I had previously worked on and asked it to incorporate this into the description.  Asking the LLM to simply “build this WordPress plugin” was met with a “you need to hire a developer” recommendation.  However, asking it to propose a workflow for building a plugin with these features was successful.  I was provided with a roadmap for building5 my plugin.
    4. This system worked reasonably well, allowing me to compartmentalize the steps, backtrack, retrace, revise code, working on a section, then another, sometimes going back to a prior sections at the LLM’s direction.  The LLM still tended to get lost, renamed variables/paths/directories/filenames, but it was less pronounced than before.  I did find it harder to use the “summarize and restart” strategy when dealing with a multi-step code development system.  However, it was still workable since I could upload all the code produced so far.
    5. The result was a new plugin, with better functionality than what I’d written myself 10 years before.  Here, the new strategy of having the LLM break the project into sections and providing a roadmap was particularly helpful.
  3. Strategy:  Conversational Scaffolding
    1. I mentioned “conversational scaffolding” and “frameworks” for discussing things with the LLM above.  This was an overarching and evolving strategy I use to help focus the LLM on the goals, keep it on track, and hopefully help it provide meaningful and useful replies.  The full text of my “prompt framework” file is too large to include here, but I’m happy to provide the highlights.
    2. Personas.  I assigned the LLM three distinct personas with differing backgrounds, strengths, and goals.  Their personas were defined in reference to one another, so the first would activate, the second would then review and interact with the first, after this process completed the third would be activated, perhaps interact with the first two, then it would move on.  I would say this process was rather successful.
    3. Myself.  I would describe myself, my goals, level of expertise, etc.  I found that I if I referred to myself as an expert, the LLM would not be as likely to offer me code proposals – but if I described myself as a newbie, it would recommend I hire a developer rather than tackle such a complex problem myself.
    4. Rules for Conversation.  These are a collection of 12 rules (at last count) which helped myself and the LLM interact.  The high points are:
      1. Answer Numbering, Answer Format, Eliminate Guesswork, Organize Assumptions, Conversational Review, Complex Answers, Context Refresher, Problem Solving Approach, File Structure, @Rules, and Personas.
      2. Each of these items were followed by a few sentences explaining something about how the LLM should be expecting to receive information and react.  My favorite of these was the rule “@Rules” which directed the LLM to begin it’s response by reviewing the Rules and following them.
    5. Knowledge.  There are a number of programming languages and technical topics I’m interested in and have used an LLM to address.  To this point, I solicited a list of useful resources from the LLM and started including a “Knowledge” section where I listed dozens of the most important resources for the languages and API’s I most commonly use.
    6. By beginning each prompt with the above “framework” (~10k of text) and following it up with a short description of my project or a file to consider, I found I was able to jump right into the project without having to provide additional significant background information.
  4. Task 3:  “Project Drift”
    1. This is a considerably more complicated task I will simply refer to as “Project Drift.”  This isn’t a real codename since the developer base is all of exactly one dude, but I don’t want to name the location/website for a variety of reasons.  In any case, Project Drift involves multiple user interfaces, numerous settings, database queries, data sanitation and validation procedures, administrator functions, and numerous other facets.  All of the above tasks and attempts were basically part of the run-up to this (ongoing) project.
    2. Using the LLM’s ability to open and read a ZIP file, as well as propose code, has been invaluable.  This in conjunction with my prompt framework allows me to get the LLM up to speed after a micro-restart – and it’s summarization procedures help me get back in the mindset after I’ve stepped away from the project for a few days.
    3. Since this project isn’t done yet, I can only give a progress report.  It’s going very well.  Much of the heavy lifting, scaffolding of the code, can be assembled for me, tedious database queries and chunks of code provided.  There are still large areas where the LLM is unable to be very helpful – and that relates to pinpointing a bug in the code (or between code sections).  This still requires a knowledgeable hand at the helm.
    4. As a solo-coder, having the assistance of another “persona” to keep me on track with a given section of code has been helpful.  I have only assigned three personas, but I could see adding a few more to fulfill different roles.

I would estimate Project Drift is roughly 30-50% complete, but this is still an incredible amount of progress in a very short time.  I would also estimate it has cut the amount of my development time by 90% (but on the easiest and most tedious stuff).

Software Development with LLMs

  1. Series Plugin Test for Illustrative Purposes Only
  2. ChatGPT WordPress Plugins
  3. Coding with an LLM Sidekick

  1. I know, it feels pretentious, doesn’t it? []
  2. I’ve got the same knee-jerk reaction to “visionary,” “thought leader,” “polymath,” and “futurist.” []
  3. Don’t get me wrong, some of the developers I’d hired simply disappeared while other relationships didn’t work out due to timing.  I don’t think anyone was malicious, just… busy, really. []
  4. Still, the job needs to be done. []
  5. Re-building? []

EDC Bag Materials, Designs, Etc

I’ve been spending way too much time fiddling around thinking about a new every day carry bag, but not a lot of time actually doing anything about it.  I’ve got piles of notes, lots of links, sketches, and product photos.  Here’s a lot of them:

This slideshow requires JavaScript.

My notes and brainstorming are also rather extensive:

  1. Different Potential Uses
    1. Work (laptop, charger), day trips (water bottle), hiking (water bottle, clothing, snacks), running errands / tech / game nights / art
  2. EDC Items
    1. An EDC Bag should be able to accommodate things that I’d be likely to carry about 80% of the time.
    2. Mask, sanitizer, tissue, handkerchief, wipes, plastic baggie
    3. Cell phone, bluetooth pocket, charger pouch, sunglasses, pens, small pad of paper, ¼ A4, Kindle
    4. Keys on interior carabiner, ring whistle loop/loud whistle, lanyards
    5. Interior lining for wallet with RFID blocking, zip ties, carabiner (in pocket?) for keys
    6. On outside, hotel key, BART card
  3. Design Requirements / Goals
    1. When empty, it should be as flat as possible
    2. Wide straps for comfort if carrying something heavy, plus good for stowing a cell phone
    3. Pull rings, paracord top grip handle (also this guide), quick access pockets
    4. Bidirectional, so the main features can be worn over either shoulder
    5. Reduction of metal, heavy parts
    6. Outside straps which can be keep an umbrella, roll of material, or jacket
    7. Outside zippered pouch on the inside (against the body) to make it less likely to be pick pocketed, internal loops for clipping / hooking keys, rings, lanyards
    8. Reinforced corners, grommets
    9. Laptop pouch inside which is higher, area for charger to fall lower
    10. Pouches and pockets near the top
    11. How many pockets, pouches, zippered, velcro, etc?
  4. Materials
    1. Heavy nylon or similar
    2. Internal lining with fleece, ripstop nylon
    3. TPU (thermoplastic polyurethane) or PU (polyurethane) coatings
    4. Foam for padding
    5. Paracord for draw strings, grip wraps
    6. Zippers

Custom Every Day Carry Bag

  1. My Ultimate Bag
  2. Custom Every Day Carry (EDC) Bag
  3. Sewing Practice
  4. EDC Bag Materials, Designs, Etc

Sewing Practice

About two years ago I purchased a few kits from RipstopByTheRoll.com – their Zipper Pouch Kit and their $10 kit.  They were partially for sewing practice and brush off long dormant sewing skills, but mostly for learning some new skills.  (You see, I have zipper cowardice.)

I did do a little bit of sewing at the beginning of the pandemic. 1

In learning how to get started sewing (again) I had to make sense of my sewing machine, settings, and sewing basics:

  • Brother XM3700 overview, settings
    • I had no idea what I was doing or what the dials were supposed to do.  Clockwise from left to right, they are the string tension (should stay between 3-5), left-right movement (irrelevant to straight stitches and seemingly best between 2-3 for zig zags), stitch length (between 1-3), and then the stitch selection dial (sticking with 2 for straight stitch and 3 for zig zags)
    • Using the automatic needle threader which way more helpful than I expected it to be
    • I created a “stitch sampler” where I noted the settings used for each stitch

      Annotated stitch sampler, with a stripe in one corner to orient the stitch setting guide

      Annotated stitch sampler, with a stripe in one corner to orient the stitch setting guide

    • I quickly discovered that the large Gutermann’s thread spool I’d purchased had way too large a core to work with the spool holder on my sewing machine.  Thus, I created a plastic insert that helped keep it from wobbling, which meant it would sometimes bounce right off the spool holder.  It was a little wobbly, so I printed a second one which worked beautifully.

      RBTR zippered pouch, and spool adapters pictured

      RBTR zippered pouch, and spool adapters pictured

  • Zipper sewing foot
  • RBTR $10 “Stuff Sack” Kit

    RBTR Stuff Sack

    RBTR Stuff Sack

  • RBTR Zipper Pouch Kit

    RBTR Zipper Pouch kit, all zipped up

    RBTR Zipper Pouch kit, all zipped up

  • When it comes to the guides by RBTR, I really have no notes.  Their video guides are helpful, detailed, and very accessible.  I got over my zipper cowardice very quickly by just watching the video a few times, letting it play while I went slowly, and pausing to go over each step.  I’m hopeful I’ll be able to use the skills I’ve developed here to build a new EDC bag.

Custom Every Day Carry Bag

  1. My Ultimate Bag
  2. Custom Every Day Carry (EDC) Bag
  3. Sewing Practice
  4. EDC Bag Materials, Designs, Etc

  1. I sewed a mask for a friend of mine before realizing (re-realizing?) I’m not great at sewing and I could do more good helping people who were good at sewing make masks.  After learning about bias tape makers from @Raster and Hackaday, I printed and gave away perhaps 200 or so in the CA area []