News for hackers. Stuff that matters.
Re:I do not use a debugger by Terr_ on Tuesday June 21, 2016 @06:56PM (#11950143)
I dunno, I mean, I'm sure you could learn to build internal combustion engines through trial and error, assembling them, letting them run, listening, stopping them, and opening them up again...

... But wouldn't it be even better to learn by assembling one with transparent materials and a magic device that could "pause" the whole engine at an arbitrary point in time?

While it's true that it will enable some students to simply "fiddle until it works" without understanding, I think that's a small price to pay for the benefit it brings to the genuinely-curious students.

Re:I do not use a debugger by banku_brougham on Tuesday June 21, 2016 @09:14PM (#11950909)
here is the crux, for me.

understanding the thermodynamics of gases and mechanical properties of steel are what help you build a combustion engine. i think this is the point of the article, that stepping through code doesnt help you understand why things happen.

when you know that pressure is proportional to the temperature and the inverse of the volume, and that steel yields at 36K psi, you understand why the piston shaft keeps breaking. those transparent materials and magic devices lets you watch the engine block crack in slow motion -- do they help you learn why that happened?

Re:I do not use a debugger by xg15 on Wednesday June 22, 2016 @05:01AM (#11952404)
You need to know those properties. But they are usually a strong simplification of reality. They will help you not to completely botch your engine design. But the see-through engine could also show you that your particular design of the pipes leads to pressure being above threshold at that particular point - and can give you clues to investigate further.

Which I think is why the closest equivalent to magic see-through engines - simulations - are actually used in engine design.