Brain Panini

Oh my, keyboard follows the mouse cursor as well? And copy/paste? I’m SO HAPPY I’m returning to Macs. Too damn fun.

TFW you discover completely by accident that the mouse you use on your Mini will pop up in your MacBook that’s sitting to the left of your Mini’s monitor if you keep dragging the cursor to the left. I didn’t set that up, but holy crapola, that is AWESOME.

I suppose it's worth noting that I enabled my ChatGPT account in Xcode? Maybe the AI integration is causing the app to crap all over my good mood? Hard to say. I have...complex thoughts about AI, but I have a hard time blaming it for what I've experienced in Xcode 26 so far.

Yeah, I updated Xcode to version 26.

Yeah, I've searched for instructions to downgrade to the previous version.

No, I don't think this is a good idea.

Yeah, I'm hoping that Apple gets enough pushback on this release that they'll fix it VERY quickly.

What a mess.

Rejoin Twitter after years away from it.

“I want to write an app that will only show me Twitter content that I want to see, not what Twitter wants me to see.”

Check cost of “hobbyist” API access.

“I want to write a Bluesky app that will…”

I'll blame my previous "pfft" playgrounds attitude on one dumb thing: I didn't realize they run previews. Not as pretty as XCode editor previews, but whatever, they work. All this time I figured they were only really good for non-UI code. Duh.

It's clear I'm slow on the uptake, but even my feeble brain should have understood the value of XCode playgrounds by now.

I'm going through Day #50 of #100DaysOfSwiftUI and I now want to go back to the beginning and start building a library of playgrounds covering all the things. Hm...

Wednesday Season 2 isn’t quite what I expected, not that I know exactly what I was expecting. It just seems to be coming up short in a very general way.

Maybe the school story line is played out. It’s feeling like Dark Harry Potter to me.

I just blocked my company’s CEO on LinkedIn to stop all the “connect/follow this person” nagging. What could possibly go wrong?

Day #49 of #100DaysOfSwiftUI FINALLY gets into requesting and displaying data from the Internet. I've been waiting for this stuff since the beginning. So far, not too difficult. Kinda easy, to be perfectly honest. Hopefully it won't go sideways on me. I've been surprised before.

On a brighter note, I managed to install the Github Copilot for Xcode extension/plugin/doohicky. I use Copilot quite a bit at work. It's great for getting you 60%-70% toward a possible solution for small coding tasks. I mostly want code hints without messing with web browsers. Could be a cool thing.

Okay, wrapped up my Health Tracker project w/o bothering with the click-to-increment-number challenge. It's basic, and it's all I can fit, and I'm fine with that. That takes care of Day #47 of #100DaysOfSwiftUI.

Day #48 was an interesting WWDC talk by PH. I appreciate the break. Now, sleep.

Okay, so my status for the day: Got a Habit Tracker app that lists Activities and offers a form to enter new Activities. I'm semi-stuck on dismissing the form after save (dismiss() won't work). That's as far as I've gotten. No count button, no saving data, etc. Let's see if tomorrow's a better day.

This course is straight-up too damn much to juggle with home obligations, a full time job, etc. I'll keep going, but I'm losing steam very quickly. It's gotten to the point of no longer being fun, and that's not a good thing. Nobody asked me to do this. I'm trying to stay excited, but...

Going through the recap of all the subjects in the last three projects (I'm starting Day #47 of #100DaysOfSwiftUI), I'm finding that I'm not retaining what I need to retain, and a lot of that is the unrelenting nature of this course. It's solid, but it's beyond exhausting. I'm getting worried.

Day #46 of #100DaysOfSwiftUI wraps up project #9 (Navigation). I got through two of the challenges fairly easily. The final Moonshot challenge will wait for another day. (Re: the second challenge, I think it's awkward making the title of the new expense an editable nav title. I'm not a fan.)

(...cont) Provide consistent back-nav and who knows how many Android users would consider iOS. Lots, I would guess. So far it's driven me just a WEEEEEEE bit crazy.

Seriously, this is a UX hole that needs to be plugged, stat.

Otherwise, iOS os gorgeous and works like a charm.

(...cont) I recall years ago how Android users would poo poo iPhones because "there's no BACK button". There isn't really a back button on Android by default anymore either, but swipe from the right = back nav. Does iOS have that? Hell no. Why? Who knows? (cont...)

In other news...over the weekend I traded in my Pixel 6a for a spankin' new iPhone 16e. I'm happy to be experiencing iOS again (I was an iPhone guy for years, until I wasn't), but I confess a significant amount of disappointment over the unexplainable lack of consistent "back" navigation (cont...)

Wow, Day #45 of #100DaysOfSwiftUI was really short. Navigation customization primarily, and because there isn't a ton of stuff you can do with it style-wise at the moment it blew by fairly quickly. I'm not sure why users would need to edit a title but I've been surprised before.

Day #44 of #100DaysOfSwiftUI has me scratching my head a little. Navigation destinations are cool but I'm not groking how the code works based on how it reads. I'm also umclear on the @Observable PathStore class, particularly how persistence works (isn't there more to it?). So much to learn...

Day #43 in #100DaysOfSwiftUI is where we finally dig deeper into navigation, or at least begin that journey. It's about time, too. I've been using navigation code quite a bit in this course but it's required extra thought and I've been assuming I missed something early on. Nope, digging in now.

Done! The final day #42 challenge in #100DaysOfSwiftUI has been conquered! Not that it's a huge endeavor, but I take my victory laps when I get the opportunity no matter how lame they may be. Being honest here: I had more fun catching up and doing the challenges than I had doing the project. Weird!

Man, Day #42 of #100DaysOfSwiftUI was a long time comin'. I took a long break so I reviewed all of Project 8 (Moonshot) and then wrapped up with Day #42. More than 1 hour, and I've not yet completed the final challenge of switching from list to grid layout, but I'll get to it (button toggle works!).

Oh hey, it's been a while, huh? I was out of town on family business, now I'm coming down with something (fun!) and work is insane. I'm getting back to SwiftUI soon or I'll die trying.

Oh, one more thing: I'm kinda pissed that Brainpan, Inc. isn't available as a company name. WTF.

Onward.

Stock market's on a tear. I'm now only [checks brokerage] 10 years behind in retirement savings!

Good thing our house is worth something. Or, perhaps we can eat it when we retire. If a house is old enough, you can eat it, right? I think I read that somewhere.

Day #41 of #100DaysOfSwiftUI ran through creating some SwiftUI views and navigating to them via NavigationLink. I'm seeing how this all fits together, in spite of it all feeling like it's a normal size donut buried under a pound of frosting. When this is over, my first project will make it all gel.

Day #40 of #100DaysOfSwiftUI saw our intrepid explorer (me) once again drinking from a fire hose. Tons of great stuff, including extensions and generics and lots of Codable goodness and holy crap a FLOOD of info. The work is definitely reaching a point where re-watching vids is a requirement.

Adding "drywall repair" to the Pay Someone Else To Do It You Damn Fool list, right underneath making sushi and re-roofing houses.