> Give a man a fish, and you feed him for a day. Teach a man to fish, and you feed him for a lifetime.
Or in the context of AI:
> Give a man code, and you help him for a day. Teach a man to code, and you help him for a lifetime.
The physical demands are real, you will likely have back/neck problems from leaning into engine bays, looking up constantly, contorting your body to get at a bolt or connector.
You are constantly exposed to toxic fumes and chemicals in the air and on your skin. You will be burned from hot exhaust, cut open on dirty rusted metal, bruised from impacts or falling objects, hearing loss from air lines hissing, air tools and hammering on parts. Those are the lucky ones... unlucky ones get eye injuries (even with 'safety' glasses), severe burns or cuts and broken bones from crushing injuries or even death from a variety of sources.
The pay structure promotes cutting corners and speed. You are paid X hours for a task even if it takes you X*2 (oh no!) or X/2 (oh yeah!) hours. You don't get extra time and pay to clean dirt and mud from an area to prevent contamination or just do a good job in general.
Vehicles are generally designed to be easy to assemble, not repair. This is why a mechanic may spend 5 minutes cutting a hole in a plastic fender well to access a bolt and plug the hole afterwards. That bolt is easily accessible when the engine is removed, but dropping an engine (they come out the bottom easier) can take 2 hours. With a shop rate of $100/hr+, you'll want the quick hacky fix to replace that $10 gasket.
Often, there is no workaround like that, so you're racing the clock... hoping something else doesn't break along the way or you get hung up on a rusty bolt. And when something does break, you hope to any god that will answer you that you can get the part in a short amount of time.
$160k is not enough for some of those talented guys... they are like professional athletes in the sense that it's a young man's game and your body is getting used up every day you're in there wrenching.
Lead fuel was during a time when the cylinder heads were mostly cast-iron, and the valve seat was cut directly into the head. Cast iron is an interesting material, it's reasonably durable, but it corrodes/rusts very easily, especially when exposed to moisture. Gasoline and ethanol both have water as combustion byproducts, so when the engine is off and cools, some of that moisture condenses inside the engine.
Running straight ethanol in an engine without corrosion resistant materials causes much more wear over time because it tends to strip the protective/lubricative oil barriers away, causing iron to corrode when the engine isn't running. Modern engines are aluminum heads with valve seat inserts, stainless steel valves, better piston ring materials (high chromium I think? these were cast iron in the past).
Ethanol has a significant detergent/cleaning effect, even when at 5-10% concentration in gasoline. The valve stems also get some of their lubrication from the fuel, and gasoline is basically a thin oil, and provides protection to mechanical components, better yet with additives. Ethanol is also a difficult fuel in a cold start situation and requires good compression and a strong ignition system to kick it off.
I suspect the whole reason to want to keep lead was motivated by the bean counters involved. They saw a cost savings with lead in the fuel. Cheaper materials and no tooling changes. This means more profits.
IMO, the best way to "handle identity across Windows and Linux" is Microsoft's own tools. You can join Windows, Mac, and Linux machines into Entra now. For $8 a month you can get an F3 license for a user. This gets you the MS Office Suite (web only) plus Intune/Endpoint Management for 5 active devices, licensed Windows 11 Enterprise (good for machines without an included windows license), the ability to control Device Policy and Conditional Access Policy. The F1 license ($2.25) might work, but don't quote me on that (read-only office, no mobile apps, no Windows Hello for Business).
Mac and Linux machines aren't as robust as Windows for endpoint management. But the core features you'd want are mostly there. Apple business manager is needed and has to be paired with Entra, but it's not completely terrible. The Microsoft documentation is actually very helpful here.
Seriously, I completely agree with you.
Rather: don't grade homework. Make the homework rather the preparation that if you did it seriously will prepare you for the test (and if you didn't do it seriously, you won't have the skills that are necessary to pass the test).
Take away the internet. Except in a research/library scenario. Give them a limited time to complete tasks. This would promote a stronger work ethic, memory/recall and more realistic to time management skills. They need to learn to rely on themselves, not technology. The only effective way is to remove tech from the equation, otherwise the temptation to cheat to compete/complete is too strong.
Don't just trust it. I've done websites as sample projects to work with LLMs to understand them better.... and while sometimes brilliant, they can miss really obvious things. One time it did user login but never actually verified the password set for a user login.
Treat it like an intern/assistant, not a magical thing that does work for you. While sometimes brilliant, they can miss obvious things, especially if you don't hold its hand. Verify, verify, verify.