**Kyle Rankin** @kyle@librem.one · Dec 20, 2019, 00:58

**Kyle Rankin** @kyle@librem.one · Dec 20, 2019, 00:58

Kyle Rankin @kyle@librem.one

Dec 20, 2019, 00:58

Fun rhetorical challenge for you:

Describe/explain something technical so that someone non-technical can understand it, but also so that someone technical can't criticize it for being imprecise.

**ruff** @ruff@librem.one · Dec 20, 2019, 07:30

**ruff** @ruff@librem.one · Dec 20, 2019, 07:30

Dec 20, 2019, 07:30

ruff @ruff@librem.one

@kyle that's mutually exclusive requirements. And is exactly the reason executive summary, high level solution design documents and such exist.

**ruff** @ruff@librem.one · 2019-12-20T07:42:11Z

ruff @ruff@librem.one

@kyle But! it does not remove necessity for low-level design documents, technical reference dcos, blueprints. Providing one (HL/LL) without the other (LL/HL) - that what brings criticism.

Dec 20, 2019, 07:42 · Web · · ·