Re:Code is Engineering; Types are Science
by taneq on Monday April 06, 2020 @02:50AM
(#22791412)
If code is engineering, then types aren't science; they're electronic design rules. Coding without types is like trying to design a printed circuit board without a 'check widths and clearances' button.
[ Parent
| on HN ]
More like without "check for disconnected circuits" button.
That too. Usually your 'DRC' button will check for unconnected signals, shorted signals, clearances, and a bunch of other stuff that I've never used. Having the ability to enter a bit of metadata and then have the computer automatically and almost infallibly check your work is one of the best bits of CAD.
Re:Code is Engineering; Types are Science
by mannykannot on Monday April 06, 2020 @08:52AM
(#22793254)
I like the way you think, but maybe it can be flipped around: types are engineering, and code is... assembly? fabrication? Putting together a product is still part of engineering, but it is not called engineering if it is done on a 'try it and see' basis.
Code is more like hot rodding- you throw stuff together, making design decisions by the seat of your pants except for a high level plan (which stays very malleable)
It's very different than the 'conventional' engineering that goes into building a competitive race car