A few thoughts while reading this: In addition to a deeper understanding of engine manufacturing considerations than I even knew I cared to learn, this article helps me appreciate why people are into engine work. The perfect tolerances and synchronization of these machines makes me a little ashamed to use the word "engineer" in my title of "software engineer". There is no real comparison of the quality of the result.…
Excuse me, but modern CPUs are way more complicated than this, even if you only look at "arranging events in time". Like several orders of magnitude more complicated. Anyone who has touched VHDL/Verilog knows how delicate signal propagation is, and how crafty you have to be with the clock. And even if you never tinkered with transistors surely you've at least looked at assembly code, and the amount of painstakingly d…
Re: Internal Combustion Engine
#321It's easy to dismiss the difficulty of something when all you see is a webpage explaining things very well and simply with some cool graphics. That webpage looks really cool, but this is just a front page of the result. The backend of all the math, equations and thoughts involved wouldn't be so visually appealing. This is just the pretty part result. If you would delve into the actual math and physics that was required for this I'm pretty sure you'd reconsider that statement. Just the study of vibrations alone is probably as difficulty as whatever you're talking about. And that's just one of several areas of study that needs to be considered when making a machine like this. Then you need static mechanics, dynamic mechanics, thermodynamics, fluid mechanics, knowledge of manufacturing processes, materials, among others. And each of these topics is HUGE in itself. You probably have no idea because you're a software engineer? It's easy to defend our own realm and dismiss others, when we know little about others' or all we know is based on some cool animations we saw on the web once.