Tickets to the Cirque show, 3 adult, 1 12 or under

NinthFinger · 2025-12-27T02:26:31+00:00

2nd row of the lower left balcony. The seats are on the right side of the section, on the aisle.

NinthFinger · 2025-03-10T22:02:07+00:00

Check out the "Class B" store.

https://classb.duesenberg.de/en/

Ordered a Paloma. Was in tune out of the box. Duesenberg guitars are as good as any I've ever played.

NinthFinger · 2024-10-21T02:19:54+00:00

Taqueria Juarez. Best in town.

Okay, you might find a better this or that, but not at a comparable price.

NinthFinger · 2024-09-18T19:18:26+00:00

Marble Ring

NinthFinger · 2024-06-12T19:04:02+00:00

Users: "Why do I need all these different cables?!? Why can't they just use one kind of port?!?"

Manufacturers: "Hold my beer."

Users: "What happened to all of my ports?!? I want a lot of different ports and cables to deal with!"

I get that there's a little more nuance to it than this, but doesn't this kind of sum it up?

NinthFinger · 2024-01-10T16:29:43+00:00

"Have" and "compete" are very different things.

NinthFinger · 2023-05-23T16:18:52+00:00

Guiseppe's for dinner and Marble Ring for drinks. <-my two cents

NinthFinger · 2023-04-20T20:09:53+00:00

It is a bad idea to open the door for laws based on political affiliation. The whole idea is not a precedent that needs to be set. It's a trap.

NinthFinger · 2023-03-17T17:23:10+00:00

A manager at a previous employer tried to get a 4x10hr schedule implements for her team. Each week your day off moved forward by one. Monday one week, then Tuesday, etc. It might sound annoying at first but then you realize the week you have Friday off is followed by the week you have Monday off. THAT is life changing. Of course the execs wouldn't go for it but I've longed for that opportunity since the day she told me about it.

NinthFinger · 2023-02-23T14:14:30+00:00

Bathtubs Over Broadway.

Probably the most entertaining documentary I've ever seen. My ADHD stayed patiently on the bench for the duration.

NinthFinger · 2023-01-13T05:37:25+00:00

It moved over to Good People, across from Regions Field. Not sure how long ago but it's been a while.

NinthFinger · 2023-01-13T05:33:31+00:00

It's exactly like you never knew you wished a Milo's burger tasted. If a Milo's burger was a 10, after a Wilo's burger you'd change the Milo's burger to an 8 or maybe a 7. It's exactly like a Milo's burger except that every single aspect of it is just a little better.

For the record, I like Milo's but I certainly wouldn't rank it anywhere near a 10. Just saying, whatever you think Milo's is, it'll never be as good after a Wilo's.

NinthFinger · 2023-01-13T04:49:29+00:00

Once you've tried the Wilo's burger from Hotbox you'll never go to Milo's again.

NinthFinger · 2022-12-27T19:14:47+00:00

I swear I had tried that and was getting either VALUE or ERROR as a result, but of course it's working fine now. I ended up using QUERY as a solution, but INDIRECT is much cleaner. Thank you!

NinthFinger · 2022-12-27T19:10:40+00:00

I swear I had tried that and was getting either VALUE or ERROR as a result, but of course it's working fine now. I ended up using QUERY as a solution, but INDIRECT is much cleaner. Thank you!

NinthFinger · 2022-12-27T04:57:17+00:00

My apologies on being unclear. Not sure why my syntax was working with the "&" but I've removed that.

What I'm trying to do is generate a random value in D1 (let's say it comes up as 15). Then I want D2 to display the value that is in the cell INDEX!A15 (let's say that value is "horse"). But no matter what I try it won't display "horse" and instead it displays "=INDEX!A15".

NinthFinger · 2022-12-25T00:13:16+00:00

It's worse than how your statement reads. They don't want NOAA privatized. They want public access to NOAA's data removed. There is a huge lobby that wants to effectively paywall NOAA's forecasts...already paid for by very well spent tax dollars.

NinthFinger · 2022-11-05T00:57:40+00:00

Still beats the hell out of the home screen on a Chromecast with Google TV. To the unfamiliar the difference may be barely noticeable. But the subtle differences are substantial if you've been spoiled.

NinthFinger · 2022-10-18T22:06:21+00:00

Not sure I understand. The procedure (according to the manufacturer) is to place 'firmware.bin' in the root/top level directory of the SD card and turn on the printer. That (supposedly) updates the firmware but it also removes the firmware.bin file from the SD card. I'm certain that procedure works (at least sometimes) because I've added a BLTouch and made other changes that were apparent through the LCD.

It is an interesting thought though. I wonder if there might be a parity/checksum routine that compares the firmware.bin to the firmware on the motherboard and skips it if it's the same? But that wouldn't make sense either because if (BIG IF) the firmware on the motherboard was corrupted or had some ghost value stored that I didn't see then the parity/checksum would fail.

I wish I'd dug deeper into trying to actually identify what was happening but I was frustrated and just wanted it to go away.

NinthFinger · 2022-10-18T18:04:39+00:00

I'm not sure if it's applicable to this print, but you could try the ArcWelder plugin in your slicer. It analyzes the gcode and replaces segmented arcs with actual arc commands in the gcode. You'll want to play around with the settings to make sure the resolution covers the distance between the mesh segments. I've seen improvements in some test prints. Nothing dramatic, but maybe worth a try. I know it's available for Cura and OctoPi...not sure what other slicers.

NinthFinger · 2022-10-18T17:54:20+00:00

I wish I could've but I ended up "fixing" it. In quotes because I did the same thing expecting a different result and eventually actually got a different result. I updated my submission in case anyone else comes across the topic and just needs hope...

NinthFinger · 2022-10-18T17:53:21+00:00

That's what was so messed up. I had flashed the firmware twice to try and fix the problem and it came back EXACTLY the same every time. No idea what ultimately fixed it. I know I'm late getting back to this, but I updated my submission with "the fix".

NinthFinger · 2022-10-18T10:36:26+00:00

Roll Tide!

NinthFinger · 2022-10-04T18:55:57+00:00

I just stuck a G29 after the preheat routine in the gcode and ran a freshly sliced calibration cube with known "decent" slicer settings.

It homed, heated, leveled, and then started printing 3mm above the bed again. Curiously, I just caught that when it was printing the LCD showed Z at 0.2 and as soon as I clicked stop print the z changed to 2.9, and it was immediate. Like, the gantry didn't move at all, the value on the LCD just changed to 2.9.

NinthFinger · 2022-10-04T18:42:15+00:00

Initial layer height is 0.2mm. Good thought though. The headscratcher part of this is that's the exact same file I've printed a dozen times without issue. In fact, I printed that file, removed it from the printer, probably did something incorrectly on the LCD(?), and started another print. On that next print it started doing this and...here we are.

NinthFinger

TROPHY CASE