|
|
|
|
|
|
by sota_pop
20 days ago
|
|
|
A good tool is invisible such that it is highly opinionated and nails the 80, 90, 99% use cases in terms of making assumptions regarding logical defaults. Restated, the tool understands the process and what a “good” result/outcome looks like. It correctly presumes relevant and important information (especially given the current stage of your full task), and can “fill the gaps” between start and finish. A good tool can distinguish between what you wanted, what you thought you wanted, and what you “should have” wanted. A good tool makes it easy to do the “right” thing and hard to do the “wrong” thing. A good tool doesn’t function to be understood, but to not be misunderstood. I have spent a lot of time sitting in this question, having spent years creating design and drafting automation tools for architects, designers, and engineers in the building-design industry. |
|
|