I feel like Charlie Brown lining up for another kick, but here goes nothing - let's see if this is yet another book that brazenly uses "engineering" as shorthand for "software engineering" or if it's actually generalizable advice regardless of specialty
