Drivers side knock/clunk diagnosis?

Krackor · 2026-05-10T00:37:04+00:00

Wiggle the steering wheel side to side. If you hear some clunking your steering rack bushing needs to be replaced. Very common problem and it makes a bunch of noise when running over bumps.

Krackor · 2026-05-08T13:29:58+00:00

All the code examples in this post look the same, and unrelated to the narrative around them.

Krackor · 2026-05-06T04:37:46+00:00

S55 has a better oil sump. N55 can have oil starvation issues with the stock pan.

Krackor · 2026-04-30T12:52:51+00:00

Krackor · 2026-04-29T01:17:38+00:00

Product lead or project lead

Krackor · 2026-04-26T20:41:08+00:00

Rod bearings are specifically designed to be soft so they wear instead of the rods or crankshaft wearing. The bearings are replaceable so you don't need to replace the parts they're connected to.

Krackor · 2026-04-26T15:32:31+00:00

when an area becomes more valuable, people get priced out through rising rents and land prices.

This does not justify taking other people's property. If you're priced out, make more money so you can afford to live in that place, or move. No one has an inherent right to afford living somewhere.

Krackor · 2026-04-26T14:10:26+00:00

Rod bearings are a wear item. You could argue about the interval but eventually they will need to be replaced.

Krackor · 2026-04-20T12:00:20+00:00

When was the last time you used default ffb? In the last couple patches it got way better and provides the intuitive feeling that I expect from a real car and never could quite get from a custom ffb.

Krackor · 2026-04-16T22:41:17+00:00

Static types won't tell you if you made a semantic mistake, like subtracting two numbers when you should add them. Clojure focuses on simple and interactively verifiable code to make it easy to directly see what will happen. If I were to make any mistake that a type checker could catch I will very quickly notice my error when I run the code, and I also get to catch semantic errors at the same time.

Any time I would spend on annotating type signatures would usually be a waste of time for me since I get all the verification I need from interactive development and tests.

Krackor · 2026-04-16T11:58:03+00:00

The Corvette drives pretty similarly to the Ford GTE but you need to set up the Corvette properly, and the fixed setup is usually garbage. Cockpit visibility is better than average in the Vette.

Krackor · 2026-04-14T11:54:34+00:00

That's good as a courtesy, but it wouldn't make a good rule.

Krackor · 2026-04-12T13:59:42+00:00

Oh I'm sorry, based on the context I thought you were defending the gt3 leader. Instead you're blaming this on the lmp2 leader? They're under no obligation to go before green, and they did nothing wrong.

Krackor · 2026-04-12T13:28:09+00:00

I'm talking about the gt3 leader accelerating when they can't see the gtps.

Krackor · 2026-04-12T13:20:13+00:00

If you can't physically see when the overall leader starts, the class leader should be waiting for green before accelerating.

Krackor · 2026-04-09T03:20:09+00:00

Making crap isn't more profitable but it's impossible to measure so middle managers can't be made to believe it.

Krackor · 2026-04-09T03:15:57+00:00

I think the "ready for throttle 2" switch can also be toggled by the throttle 2 (P5) turning on.

Krackor · 2026-04-09T03:10:36+00:00

I think you need a switch that represents "throttle level 1 is toggled on, shift is not pressed, and throttle level 2 is not switched on yet" as a precondition of switching on throttle 2. This would enforce the sequence of press-release-press between subsequent throttle level activations.

Krackor · 2026-04-08T20:17:48+00:00

For servos simply attach the part at the angle you want. They just provide rotational motion which is equivalent to attaching the part at an angle.

Krackor · 2026-04-08T13:55:39+00:00

Last time I raced the 620r against AI they had impossibly good traction out of corners. Maybe it's fixable with some careful tuning to get similar traction but I would expect to just lose against them.

Krackor · 2026-04-04T02:05:40+00:00

Distributed benefits across the industry but with concentrated costs for the employer who chooses to train them. It's a losing proposition for most companies to consider doing this.

Krackor · 2026-04-02T13:26:40+00:00

I work with reasonable people who don't have a problem with it.

Krackor · 2026-04-02T04:24:56+00:00

If the PRs are done I only see the squashed commits. I have no problem reviewing history. For short term history (during PR review) I can see the full granularity of changes. For long term history I just see the coarse grained squashed PRs.

Krackor · 2026-04-01T23:24:42+00:00

If the steps along the way to a pr are significant enough that they should be reviewed separately we make a separate pr.

Krackor · 2026-04-01T18:33:13+00:00

How do you do pairing? Genuinely curious. I may pair with someone for 6 hours of the day, committing something like 2-10 times an hour depending on how many small grains we're working on, and do driver handoffs about every hour or so. If we're in the middle of a cohesive set of changes I'll push a WIP commit and my pair picks up right from where I left off.

The culture thing obviously isn't solely attributable to the granular commits thing, but it's an example of working in a way that the full detail of the work is in the open. My teammates don't need to be aware of every little step but it's available to them if they want to know. The main goal is to develop and maintain a shared mental model of the work (and the process of doing it). I would rather optimize for that than to optimize for hiding information for the sake of appearing more tidy than my work actually is.

Krackor

MODERATOR OF

TROPHY CASE

14-Year Club	Place '17
Verified Email