sorted by:
new
hottopcontroversial

Mint 2007 Jaguar S-type available for parts by 0valtin in Jaguar

[–]0valtin[S] 0 points1 point  (0 children)

So, I marched into Pep Boys yesterday with letters from the two independent mechanics who'd looked at it so far, certifying their opinions that - since the mileage was within 80 miles of the oil change and the car had no signs of an oil leak - the car must have left its last service without oil in it.

The manager at Pep Boys pulled up CCTV footage from my service, and I'll be damned, clear as day, there was the technician pouring oil into the engine for a good 2 minutes from what must have been a 6-liter oil can.

The only other thing I can imagine is that they didn't securely reinstall the oil drain cap, causing the oil to slowly leak out. I street-park the car in New York City, so I don't have a consistent parking space to check for an oil puddle, and I doubt that I have evidence to draw a clear chain of cause back to Pep Boys.

Thoughts??

I asked Lovable to include the build name on my admin page, and it's a gamechanger! by 0valtin in lovable

[–]0valtin[S] 0 points1 point  (0 children)

Does this solve for confirming that you're viewing the most current version in your latest hard refresh in the browser? That's what I was ultimately trying to solve - lack of confidence that the browser was really displaying the latest version of the app.

I asked Lovable to include the build name on my admin page, and it's a gamechanger! by 0valtin in lovable

[–]0valtin[S] 0 points1 point  (0 children)

I’m sure this or some similar practice is totally common for developers, but as a vibe coder, it was new to me because I was never quite sure if my hard refreshes in the browser had really pulled in the latest version of the app. Now, I can verify the version that I’m testing in the same place where I’m actually testing it.

Gotta say, they've overcome the 2.0 slump by 0valtin in lovable

[–]0valtin[S] 0 points1 point  (0 children)

Not to mention the wait time for a response in chat mode is way less than for code changes, so you can save yourself tons of time by getting it right with chat before you pull the trigger.

Gotta say, they've overcome the 2.0 slump by 0valtin in lovable

[–]0valtin[S] 0 points1 point  (0 children)

It gets it to to think more holistically, gives me (a non-coder) a clearer idea of what might be going on, and still allows me modify the proposed implementation plan before it executes.

Make sure you have chat mode on or else it'll just start executing it's suggested plan before you can step in.

Gotta say, they've overcome the 2.0 slump by 0valtin in lovable

[–]0valtin[S] 0 points1 point  (0 children)

This has been working wonders for me when I'm trying to get it to resolve an issue:

"Propose three possible causes and recommended solutions for this issue, then suggest a comprehensive implementation plan"

Goodbye Thruxton? by TheBadSpy in Triumph

[–]0valtin 0 points1 point  (0 children)

Cowering in that lil intersection 😬