Probably means this article wasn't written by AI!
Here's their website for the book, along with some tools and useful instructional videos https://www.creativeconfidence.com/tools/
So far I'm about 80 pages in and have found it extremely academic and not very practical, sometimes deriving conclusions that are so far from reality that they are a bit concerning, like how a strong password does not matter because once they inevitably leak they can always be cracked via rainbow tables (the author doesn't use this exact term). As we know the exact point of a strong password is that it will not be in a rainbow table.
Of course the original version is pretty old but I picked up the latest revised version. Still some interesting insights and I haven't given up on the book quite yet but it's been a ton of theory and a lot of terminology so far.
PS. Refactoring UI is from the guys who created TailwindCSS.
Design Thinking is a subset of Systems Thinking (this is the polite interpretation). Design Thinking does with its sole existence what Systems Thinking tried to avoid: Another category to put stuff into, divide and conquer. It is an over-simplified version of the original theories.
Better: Jump directly to Systems Thinking, Cybernetics and Systems Theory (and if measurements are more your thing, even try System Dynamics).
I can only recommend that anyone interested in this topic take a look at the work of one of the masters of Systems Thinking, Russel Ackoff:
https://m.youtube.com/watch?v=9p6vrULecFI
This talk from 1991 is several dozen books heavily condensed into one hour.
(Russell Ackoff is considered one of the founders of Operations Research and ironically came to be regarded an apostate as he tried to reform the field he co-founded. He subsequently became a prominent figure of Systems Thinking)
My 2c. I'll show myself out.
I have to admit that it was very hard to me to follow what they were saying.
Maybe I’m dumb, maybe the person didn’t explain it well, or, maybe system thinking is really complex and thus hard to convey and use.
Design thinking on the other hand is easy to understand and apply.
> maybe system thinking is really complex and thus hard to convey and use.
I'm pretty sure that's not true. If you can follow how A leads to -> B, then that's about it all. Systems thinking is the same principle at a larger scale, with interesting side effects at times (eg network effects/group think/emergent phenomenon showing up).
kaizenb•1h ago
I've been curating (mostly design) books on a digital library: https://links.1984.design/books
jgeurts•54m ago
password54321•29m ago
If that's what you want you can just use Apple as a case study because that's what you end up getting if you want "modern" and minimal.
kaizenb•19m ago
janeway•26m ago