IMALlama

Some of those are looking pretty ripe! I like to try to get a block of time to go after the bush in long chunks, but that's not always possible. How big is yours / how many do you have? We have two. One is tiny (about 3 feet tall), but the other is pretty big/bushy (10 feet tall or so). The big one takes an hour or two to pull all the seed pods off...

Great question, it really hits at the heart of my struggle. If you read between the lines of my post, it's clear that I think more highly of the Sony. So why am I waffling? Why write a wall of text?

I haven't been able to put my finger on it, but I just don't love the Sony. It's a very technically capable camera, its ecosystem is great, and it does disappear pretty effectively when you're using it. I don't hesitate to bring it with my on a family outing. In fact, I use it way more often than I used any other prior camera.

Maybe it's the ergonomics. The OM-1, and the Z6II for that matter, have a more comfortable grip and feel somewhat better in hand. They also have more accessible control surfaces that you can use without taking your eye off the EVF. An example includes the two buttons on the front of the body by the lens mount.

Maybe it's the responsiveness of the camera. The Sony is certainly a fast camera, but the OM-1 always turns on immediately. It will also blaze away at taking photos and seems to do so just a touch faster, granted I'm using third party glass on the Sony.

All that said, the Sony is just so easy to get great results with. I was messing around with the OM-1 and A9II yesterday while my kids were building legos. My youngest held their creation up after they completed every step, often in front of their face, and the OM-1 would consistently choose to focus on the lego. The A9II on the other hand stayed laser focused on his face much more consistently with its tracking AF.

Although my heart isn't really in camp Sony, at the end of the day it's probably better to have a reliable dance partner that you work well with than a drop dead gorgeous dance partner that steps on your toes.

True Lies is truly great. There are a bunch of other good choices in there too, but true lies really sticks in my head.

Agree that the result won't be a perfect print, but I personally prefer this route over printing the other half, sanding the first half flat to account for a partial layer like you said, and then gluing.

I guess it comes down to what you goal is. 90% of my prints are functional and I don't really care if they're a bit ugly at times.

Ditto. I had no idea this knife existed, and haven't carried a knife in ages. I actually preferred clipless and this design seems super neat. $178 puts this knife back in window shopping territory for me :(

Do you have a pair of calipers that you can use to measure print height? If yes, don't take it off the bed. Measure the height of the print, delete those layers out of the gcode (it's just a text document after all), and reset. Note that the gcode and printer setup might require some fiddling to get right, but I've resumed prints like this without problems before. They don't all look perfect at this layer, but they're certain better than nothing. Once the print loses its hold on the bed, all bets are off.

I might be bias, but we (Michigan) have the best election stickers this year.

I got one!

Look more closely at the scales ;)

Thanks for both replies, they were very informative!

On the programming front, there are a couple general buckets you can fall into.

Do you tend to naturally follow logical reasoning (given then )? If yes, you're in a pretty good starting position for algorithms. Computer programs should be predictable/deterministic. This all hinges on the people making algorithms implementing them well - especially when it comes to corner cases.

Do you build excel files with tons of vlookups and the like? If yes, data structures (think database schemas) and potentially back end could be your jam. Programs store/access data. That information should be well structured.

Do you have workflows/UX front of mine? If yes, maybe your strong suite is UI/"front end" design (and potentially implementation). IMO this is where a lot of FOSS falls down - my current podcast app can show you podcasts episodes that have been released in chronological order. You can remove them from this list, or you can add them to a secondary list they call a quque which... offers basically the same functional as the first list but now that it's a separate list you have to manage. This is not a dig on FOSS. If anything, it's meant as encouragement to say that even without knowing how to code you can contribute to help the apps you use feel better to users.

If you want to get your toes wet in Android download Android Studio. It's free.

Give the Jetpack Compose tutorial a run-through.

Kotlin is what happened when Oracle sued Google about using Java to anchor Android development. The link above gives a decent programming 101.

Finally, if you live close to a local community college, signing up for a few programming classes might be pretty helpful.

This was a good read. Anyone who'se purchased any of his anthologies will be familiar with some of the content, but the appeal to live a fulfilling life and how hard that can be as you get older was refreshing.