|
|
|
|
|
by aatd86
914 days ago
|
|
On the contrary, I've found the article quite refreshing. Using eigen isn't such a big issue if you understand it as the eigen in eigenvector. It's about implementing orthogonal features i.e. Solving non overlapping concerns. Having one way of doing things. Make things easier, less cluttered. The exposé is right on the money and actually even explains it. Perhaps the faux intellectualism is on the other side... <_< |
|
> the eigenquestion is the question where, if answered, it likely answers the subsequent questions as well.
> This inspired me to name a symmetrical concept I’ve been pondering for a while: Eigensolutions. The eigensolution is a solution that addresses several key use cases, that previously appeared unrelated.
The original article is a complete muddle. It misdescribes framing, and then adds in a misdescription of eigenvectors. It's spending a lot of time and effort on misuse of language to no benefit -- plausibly the motivations were pseudo-intellectual, or at least, intellectually lazy.
The reason it has to do this is obvious: describing breaking problems down, framing problems, and asking fundamental questions isnt new; and no person discussing that seems impressive or a genius.
Throw in a few half-baked borrowed notions from rhetoric and mathematics, however, then it all seems so much more vital.
The whole thing is an exercise in writing 5x as much to say 1/2 of what's needed and playing to a dumb audience ready to lap it up. The dumb audience in both cases are non-tech manager types, who're endlessly desperate to acquire technical language to seem in-the-know.