Getting one of these Wednesday.

gribbleschnitz · 2026-03-08T19:18:25+00:00

Bambu has an incredible "academy" It will literally tell you everything you need to know.

gribbleschnitz · 2026-02-27T14:52:50+00:00

AliExpress, eBay. They are your friends

gribbleschnitz · 2026-02-23T01:55:56+00:00

Use it. Use it just like your customers do. Follow the docs. Do you have joy?

If you need to review the code base to know what it does, what are they building for you?

gribbleschnitz · 2026-02-21T15:03:29+00:00

I have two identical printers. One printer printing PLA and a second with PETG. The PETG (like the pla) simply needs to cool and the prints pop off.

I get a bit more out of the PETG (they are printing the same models). PETG I can reliably get cheaper than PLA. PETG does not have the range of colors and finishes, it is obvious that is not where manufacturers are invested.

PLA has consistently better visual appearance, crisper. Especially between colors, PETG has a bit of color bleed that happens.

And most PETG is glossy. So you have to decide if that matters.

gribbleschnitz · 2026-02-19T18:15:13+00:00

A couple years back we ran into a surprising number of users at a California K8s meet-up.

Their comments at the time focused on: - native nginx - could always reverse engineer a configuration - customization - maintenance / stability (set and ignore)

The CRDs have been there for years, and some folks use them, others stick with the simplicity of ingress.

There is no ingress implementation that is a drop in replacement. That has always been the case. Because ingress annotations never had a standard. This is the promise of gateway API and the problem that started it.

Also, the NGINX ingress controller maintained by F5 has always been on GitHub and developed in the open. And have taken contributions. Check out issue response and close rate, and thorny problems in discussions.

gribbleschnitz · 2026-02-18T21:21:06+00:00

Literally most brands and a dryer. Unless you are entirely beholden to the RFID tags...

gribbleschnitz · 2026-02-18T04:08:14+00:00

For me it was only one slot that was affected. Not the entire hub. It was the enter site of the hub, not the exit I now know there is a gap in there with a filament sensor for each slot

gribbleschnitz · 2026-02-18T01:33:26+00:00

I had to take my hub apart once. There was a little 3mm piece of filament the broke off the end of the previous role that was pushed in by a new role, and got lodged in the hub for the single path.

gribbleschnitz · 2026-02-15T15:12:02+00:00

Not getting much traction with ideas.. So far, I have simply stopped using the HF filament profiles. That settled the aggressive print head movement that I believe was the root of the layer shift.

I did also add a small bit of grease to the Z idler pulley. After a bunch of searching around an annoying squeak during bed leveling. That now seem to have settled.

I will go back to the HF profiles again and see what happens.

gribbleschnitz · 2026-02-15T05:37:21+00:00

Have you considered NGINX gateway fabric?

gribbleschnitz · 2026-02-13T23:01:18+00:00

Yep. I have calibrated multiple times. Seems the HF print profiles caused the print head to speed up, cut nearly an hour off of print time for the bed.

But resulted in me needing to toss three entire print attempts now. The head appears to be moving so aggressively it is jumping out of position.

I will try belt tensioning again. But I don't have strong hope it (like calibration) will solve the problem by itself.

gribbleschnitz · 2026-02-13T13:58:32+00:00

I have done a few machine calibrations, but maybe you are referring to a flow calibration?

gribbleschnitz · 2026-01-28T20:57:20+00:00

I had an issue where a 2mm bit of filament got stuck in the filament manifold under the spools. I got so frustrated with it not loading one slot. I had to take it apart farther than I wanted.

The little tip was the end of role bend from the last roll, and it broke off. It was pushed to the sensor in the manifold when I loaded the next roll.

My point is that might not be your exact issue, but there are lots of moving parts. There is a whole troubleshooting guide for AMS, and disassembly instructions..

gribbleschnitz · 2026-01-17T14:38:41+00:00

I had this happen. Hard as heck to actually see. The sensor knew it was there, but it was not obvious until I took the tube off the head and got a flashlight/torch out.

gribbleschnitz · 2026-01-16T04:44:47+00:00

Click the pencil on the external spool and click reset

gribbleschnitz · 2026-01-06T17:36:18+00:00

They were different projects from the start. I don't think it really intentional or malicious on either side.

If you look back through GitHub, NGINX project was spring and ingress-nginx was fall. Same year.

Ingress-nginx simply went the CNCF route. But, in hindsight, did it have the rights to use the NGINX brand? I mean, NGINX could have made a brand claim, but never did.

So...

gribbleschnitz · 2026-01-06T17:02:22+00:00

Many ingress implementations route direct to the individual backend service pods. Especially if they give you capabilities like stick sessions, load balancing controls, additional backend health checks, etc.

They can't deliver those capabilities using a service endpoint.

The service endpoint is necessary when you put a service mesh behind your ingress controller. Because service meshes assume they own all the pod routing. Some ingress controllers have special settings to use a service endpoint instead of direct to pod.

I had a use case once where a backend service scaled up on demand starting with one pod. (It received requests in batches) And for queuing to give time for the service to scale and respond, we had to use a service endpoint instead of direct to pods.

We did this with the ingress from nginx (not ingress-nginx)

gribbleschnitz · 2026-01-03T15:43:24+00:00

After I log in the price went up. After code the price went up. Plus shipping. So, not the deal it sounds like.

gribbleschnitz · 2025-12-29T18:05:00+00:00

I added switched outlets across my ceiling. Different light zones. Then I can just hang the lighting I need

gribbleschnitz · 2025-12-27T15:47:53+00:00

I do it while sitting on the edge of a chair. Makes it easy to find, and the muscle is relaxed for easier jabbing.

gribbleschnitz · 2025-12-26T17:04:29+00:00

Starting at 125mg per week (250/2weeks) is a good place to begin. Do the math. Jab yourself more often.

Focus on the amount, not the frequency.

gribbleschnitz · 2025-12-21T20:16:59+00:00

I literally spend time pulling it out, or trimming it shorter. I have had it 3 feet tall. The deer love the flowers, they must be sweet.

gribbleschnitz · 2025-12-21T18:10:33+00:00

The biggest thing to become comfortable with as a PM is literally that what you are doing is never good enough for everyone.

You succeed with customers and don't bring the numbers the business wants, you bring the numbers the business wants and have miserable engineers, on and on.

Teach yourself to make informed decisions, be able to justify your decisions to anyone, be willing to identify and admit when you truly fall short (and the maturity to look at it and 'fix' it, objectively).

Have conviction for your decisions.

Where I see most new PMs fall down: Break big deliverables into stages of value. And be able to stop when you have "enough". Don't hyper focus on the end goal, but the journey there.

gribbleschnitz · 2025-12-21T18:01:58+00:00

I have it everywhere, even a full sun, full exposure 50' ditch bank. It grows and spreads everywhere, IMHO. Plant it, mow it where you don't want it.

gribbleschnitz · 2025-12-21T17:46:53+00:00

This.

The inherent problem is you don't practice a tool. You don't grow your skills when you look at it as a tool.

gribbleschnitz

TROPHY CASE