News for hackers. Stuff that matters.
Re:Design Docs at Google by cameronbrown on Wednesday July 22, 2020 @10:23AM (#23917297)
I mean, you're right... but the goal of an analogy isn't to be perfect, but to be a rough mental model to quickly express a concept. I think it's fine.

Different jobs require different levels of abstraction and design docs fulfil that role for software engineers.

Re:Design Docs at Google by shuntress on Wednesday July 22, 2020 @10:30AM (#23917385)
That is true but if the analogy is too imperfect then it won't express the right concept.

A bad analogy is like a leaky screwdriver.

Re:Design Docs at Google by learc83 on Wednesday July 22, 2020 @10:25AM (#23917324)
Yes models can be helpful even if they aren’t perfect. But not only is this one too far off to be useful, it does more harm than good. The expectations that happen when people (specifically managers) start thinking of design docs as blueprints, software architects as architects, and developers as builders are downright dangerous.
Re:Design Docs at Google by DEADBEEFC0FFEE on Wednesday July 22, 2020 @05:36PM (#23921881)
Models are always imperfect.
Re:Design Docs at Google by gowld on Wednesday July 22, 2020 @06:42PM (#23922359)
An analogy is a blueprint for an explanation.