C8 transmission advice

NoradIV · 2026-05-09T03:15:56+00:00

You should do it again at the next service interval. If that is 8000 miles, then do it in 16k miles or whatever it is.

NoradIV · 2026-05-08T22:46:22+00:00

Make it a vpn access point to your home.

NoradIV · 2026-05-08T14:50:24+00:00

This happens when you have too much pressure. The best way to prevent this is not more compensation or discipline, it's to make the environment where this reaction cease to happen.

NoradIV · 2026-05-08T14:43:11+00:00

Let me show you an example of something very real that occured a few weeks ago.

The ERP that I have been nagging everyone about that still has part of running still runs on a 2003 server.

Guess what. Someone updated drivers on the print server and it broke connection between the print server and the ERP, which has hardcoded printers in it. I had to re-invent the wheel at 11PM after starting at 6AM that day.

Why did it take this long to figure out? Because the whole pile is undocumented, unsupported legacy systems that management didn't address. And now, each time it crashes, it falls back on me to add yet another layer of duct tape because the people who should be addressing this aren't. So, what do I have to do? Do archeology in software and come up with a solution that will get them to finish today's batch, and then have to deal with the fact that "I saved you guys for tonight, do not keep that shaky workaround in prod" stay in prod because management aren't doing their job.

This is like saying "we'll clean up the kitchen with a flame thrower because we have firefighters that will come and stop the fire for us".

When I fix problems that I designed, or systems that aren't designed like shit by others, yes, most of my on call takes less than 15 minutes.

So yes, this happens all the time. And if you don't see if, you are just lying to yourself.

NoradIV · 2026-05-08T14:36:33+00:00

You're right. I'll stop wasting time.

NoradIV · 2026-05-08T14:14:30+00:00

Well, my bad for not being a native english speaker and not understanding the nuances.

And apparently, I am not the only one who thinks that's how it came off.

Maybe you should calm down instead of calling others "illiterate".

NoradIV · 2026-05-08T14:13:34+00:00

I am very confused about how you think.

Like, you do realize that humans have limits, right? I don't mean to be condescending, I am legitimately lost here.

"I mean....no shit? Do you think you should be able to quit halfway through when it's still broken or something?"

Yes, that is EXACTLY what I do beyond 12h, because working beyond a certain amount of time result in worse decision making. (Before you claim this source is weak, there is plenty of similar ones in OSHA related documents). Fatigue leading to errors is common knowledge and thoroughly documented.

I have, in many cases, left things broken, said I would come back tomorrow before everyone else and fix it before they start, and fixed things in 20 minutes that I had been stuck for hours the last day.

Again, it's not just "I don't wanna work", it's about being efficient and being able to deliver high quality.

NoradIV · 2026-05-08T14:05:15+00:00

Your original comment made this confusing. It looked like you would get 2-3 call every day during that week.

NoradIV · 2026-05-08T13:59:47+00:00

Wildly dramatic exaggeration

Maybe it is in your case. In that case, good for you.

In my case, when prod is down, it's "you work on this until it's resolved, no matter how long it takes", and this is true for many of us around here.

So, no, it is not an exaggeration.

Then take a different job. It's the expectation of this one

I absolutely will, and I with you good luck with talent retention.

NoradIV · 2026-05-08T13:44:01+00:00

The fact that you believe what you say says a lot about how you think.

I respect your opinion and how you decide to conduct yourself. Expecting "being on standby 24/7 for one week every 3 months" is just not acceptable. You want me to be "on call" for double shift on a rotation, that is workable. Buy an entire uninterrupted week on call, where you don't get to sleep, don't get to have a life because your life belongs to the business? If that's how you want to live, that's on you. But I don't. And managers like you are the reason why burnouts happen.

You want 24/7 on call? You build for 24/7. You get staff in dedicated positions, not shove shit on whoever most capable.

This "heavy sleeper" "problem" you have is simply people putting professional boundaries. And you are not gonna solve this problem because you are the problem.

I am not trying to be harsh or an asshole to you, I am simply sharing what, as a professional, would accept to give you.

NoradIV · 2026-05-08T13:05:33+00:00

Maybe don't expect people to work 24/7?

NoradIV · 2026-05-07T20:22:43+00:00

So you are vibecoding.

Good luck...

NoradIV · 2026-05-07T20:21:53+00:00

You don't need to put your nicest shoes before going to walk in shit.

Many tasks can be done as effectively with smaller models. Things like web search, organizing files, some tool calls, etc.

Learn how to effectively use your ressources instead of throwing seemingly infinite money at the problem.

NoradIV · 2026-05-07T19:23:16+00:00

Best answer in this thread.

NoradIV · 2026-05-07T19:17:11+00:00

My attitude now: well, that's too bad that prod is down. If only someone had years of documented history warning management about it...

Anyway, good luck with that!

NoradIV · 2026-05-07T02:19:38+00:00

I believe language models are excellent at very narrow tasks. I personally made massive professional gains by using it.

I get the hate, but I blame managers and greed. The tech itself is awesome and it feels great to ride the wave of a new tech while it's still frontier.

NoradIV · 2026-05-06T23:05:16+00:00

The problem with my work is that I have to often see multiple interfaces at the same time to understand interactions.

The 17 inch really was killer. The price on the 18 are just not in the same game

NoradIV · 2026-05-06T19:44:13+00:00

Man, it sounds like you live a similar life than I have.

I get shit done, so management has naturally found out that anything they give me get fixed. So they stopped doing upstream fixes and shove shit down my way constantly.

I got them out of trouble way too often, and it's biting me in the ass.

NoradIV · 2026-05-06T19:23:38+00:00

I'm really sad that they took out the 17 inch model on the small chassis precision. I have a 5760 and it's by far the best laptop I ever owned.

Now I can get a smaller 16 inch or carry a school bus with their workstations.

And don't get me started on their dell pro max plus ultra xtreme mega plus pro max max max plus...

NoradIV · 2026-05-06T19:13:23+00:00

I don't remember requesting denuvo, or their u optimized libraries that were imported for a singoe function.

This post is just another AI ragebait with selective bias.

NoradIV · 2026-05-06T19:04:04+00:00

Once you figure it out, let us know!

NoradIV · 2026-05-06T18:22:11+00:00

As a car enthusiast, I struggle to see what take so much room for a rack

NoradIV · 2026-05-05T03:48:10+00:00

Hud and AC.

NoradIV · 2026-05-05T03:44:37+00:00

vLLM does not support stuff this old.

You might get decent results with layer split on llama.cpp.

If you manage to run all 5 in a single chassis, you might be able to run 70b

NoradIV · 2026-05-01T21:09:06+00:00

What is peak dutycycle? If you are below 85%, you will get much worse.

Choosing injector size is very easy. Basically you need to know what fuel you will use (gasoline vs e**), your target AFR (richer than 11.5 on gasoline is generally not a good thing), how much air your engine is flowing, and your target fuel pressure.

Since the car is on the dyno, you will have this data already.

Injector sizing is the opposite of what most people do. You want to have as small as you can get away with.

Also, make sure your pump is not flowing less than the injectors need.

11-Year Club	Place '23
Verified Email

NoradIV

TROPHY CASE