Writing and things

TIL 2025.3.17

Today I learned

  • Maybe not so much as learned but remembered: Break things down.
    • I tend to over complicate things by getting into the details (a plus/minus of being so highly monotropic), but when that just results in errors I can remind myself to break it down into silly small steps.
  • Don’t forget the print tool.
    print(foo)

    • It’s such a simple little thing, and yet I (again) over-think problem solving. The print command is one of those things you can learn as a beginning coder and then just fly right past when you feel more intermediate (note I say feel here).

This reminds me of a Zen parable:

Nan-in, a Japanese master during the Meiji era, received a university professor who came to inquire about Zen.
Nan-in served tea. He poured his visitor’s cup full, and then kept on pouring. The professor watched the overflow until he no longer could restrain himself. “It is overfull. No more will go in!”
“Like this cup,” Nan-in said, “you are full of your own opinions and speculations. How can I show you Zen unless you first empty your cup?”

  • Using LLM tools are a good starting point for building better things.

TIL 2025.3.10

Today I learned

  • That I know enough about making API posts that I created one!
    • I’m working on a tool to update my Habitica To Do list with information generated by another tool.
    • I made a test POST call today! It worked!
  • Next I need to figure out how to do the harder part (maybe not that hard) of taking the data (in the form of a JSON object) and updating the info to match Habitica’s POST requirements. Maybe not so hard. That’s for tomorrow.
  • I hope this stuff is informational? I enjoy writing about it actually. This is more interesting than I though it would be!
    #todayIlearned

TIL 2025.3.7

Today I learned

  • Motivation when trouble shooting is crap.
    • Seeing the same error over and over when you try new fixes is exhausting.
    • Seeing the same error is actually good too. At least there aren’t new errors.
  • My desk step up is not very comfortable for long term projects. Time to move some stuff around and make room.
  • Short note today. I spent a lot of time the last few days getting my silly bash script to run on a schedule. Like way too much time.
    #todayIlearned

TIL 2025.3.3

Today I learned

  • That I can actually understand documentation when I read slowly.
    • I’ve had problems understanding what Apple Documentation is trying to say. It’s not that it’s written poorly, I just don’t understand exactly what it means.
    • Today I read through SwiftData docs and actually had an "OH! I know what that means" moment. AND (this feels big) was able to understand what the error messages were telling me in context!!
    • But wait there’s more: I resolved the errors! WHAT?! Yah. WITHOUT GOOGLING OR RELYING ON A TUTORIAL.
  • I also learned when working with @Model you have to initialize the object. I mean, yes, that sounds simple and Xcode will give you a warning. But not being a CS major, and understanding that still sometimes feels like a major milestone.
  • It helps to go back an relearn what a lot of CS majors might think of as "basic" information. I also have to remember that this, to a CS major, is the same as what makes up a scale to me (I was a music major in college).
    • It’s very easy for me to remember the anatomy of a major scale (whole, whole, half…ect). I started playing violin in the 3rd grade.
    • Remembering the difference between an object and the Class (in this case the model) is still a new fact that takes time to be solid.
  • I’m pretty conflicted about using LLMs and their clients still. But, I listened to a recent podcast about using tools to help make my own accommodations. Some of these tools were tools that had a LLM wrapper of some kind. So I felt less ikky about using a tool to ask it how to write a bash script to automate a task. Since bash scripting has a bit of a steep learning curve and I don’t have the energy to learn that (on top of everything else).
    • Nice bit here is I didn’t feel lost following the directions it gave.
      So that’s a LOT today. I want to publish this kind of "TIL" post, and I may restructure my blog to put these in a slightly different page. That’s for another day.

KEEP LEARNING MY FRIENDS!

#automation #todayIlearned #til

How I’m seeing it now

What I want to become

The idea that has been forming in my mind of what is comfortable and interesting to me has evolved in the last 2 years. I originally started learning Swift a few years ago because I like Apple products and have been in the ecosystem since 2001. When I was in college, I bought my first iMac (Sage) and just fell in love with how easy everything was to use. That ease really spills into Swift as a programming language. It’s unfair to compare it to older things, but the syntax is so much more friendly. I digress.

The idea that is forming for me is to be indie. Some form of an indie developer/creator. I’ve always been a maker of some kind. I do really want to make tools or applications that will make my life, and the life of people in my community(ies), easier. A big draw to this (for me) is scheduling. Currently working part time is nice, but I don’t really like working one day, having one day off, working another day, having another day off, and then working 4 days in a row. What the crap is this? Scheduling like this makes my mostly skewed since of time just go right out the damn window. What day IS IT ANYWAY?!

So making a schedule that works for me during times that feel better to work. Another draw is being my own boss. I don’t have to follow some article in the database that tells me how I have to fill out my TPS report. I can make my own format that matches how I think. Yes, I understand that if I have clients I’ll want to cater to their needs. But I can do that in my way.

Where to go

All this is brain vomiting leads me to want to put this idea out. I have realized that I am strongly monotropicand that I work very well when I focus on the things I like. The bad news is this leads to perfectionism. So in order to combat this perfectionism, I’m working on just getting stuff out there. Like before, I want to start this shit up.

This blog is an attempt to keep myself accountable for my ideas and goals. I’m working on automating things to help me remember my goals. Greasing the wheels on creativity. The lower the friction, the more I’ll just slide right down the hill. This stuff is hard y’all.