Foundation model sponsors already pay humans to generate authentic content, especially in technical areas that are underrepresented in general internet scrapes. I would imagine that this trend will continue.
Further, the "model collapse" hypothesis of 2020/2021 seems to have failed to materialize. Maybe we're still too early, and we're not yet seeing negative effects of OpenAI training on OpenAI output. But maybe "slop" is not being rewarded as much as human content, and having humans in the loop (even as readers) is preventing a slide into incoherence.
Will LLMs eventually disincentivize people from producing and publishing new original content? If that content is easily replicated by an LLM query, maybe. And maybe it's not the worst thing in the world. 5 years ago I would have bought an "FFmpeg Cookbook" from O'Reilly, but now I would just tell Claude exactly what I'm trying to achieve. As a consumer, I'm better off, and arguably we've saved the author of a hypothetical FFmpeg Cookbook weeks out of their precious life. Weeks they could spend doing something—anything—more valuable than rewording FFmpeg documentation.
Design Thinking (and more broadly, human-centered design) is a pragmatic framework for doing product design in an effective and productive manner. Systems Thinking is a massively more general superset. I'm not really sure how you'd operationalize that on a design project, except by following first principles, which would essentially get you to DT / HCD.
Taking a theory (Systems Thinking), a mental model which has the primary goal of holistically identifying, describing, and understanding wholes and reducing it down to a set of methods/framework out of ease of use (the pragmatism) is exactly the wrong approach in my opinion.
Systems Thinking and all of its applications scenarios are based on epistemology. To turn it into a recipe is a wrongdoing. The whole notion is that one size does not fit all.
The operationalization of Systems Theory for a given case at hand is the responsibility and the transfer function of the operator whose approach this is. The process itself yields understanding and should not be abbreviated.
So your argument is don't use an off the shelf tool that gets the job done, build your own tool every time which likely doesn't offer any advantage over the standard tool?
If you think using Design Thinking goes against Systems Thinking, I don't think you really get either.
> So what do you mean by "Design Thinking does with its sole existence what Systems Thinking tried to avoid"?
It’s its approach to Systems. Take the 5 stages. Why 5, not 10 or 3? Why stages at all? Who’s to say? Why not enable people to create stages themselves and run from there? Or whatever fits their business.
Why not teach methodology instead of method?
>I'm not sure why you think it's relevant here.
I can only repeat myself:
The value is in the process of inquiry itself. Systems Theory is not a set of methods. It is an epistemological based theory and requires a shift in how a person perceives reality, the often cited worldview. How do you know what you know? By assuming 5 stages? Is that objectively induced? What happens to that if looking through the lens of radical constructivism? The theory requires to incorporate multiple worldviews and with that, negates the assumption of an objective truth.
So your argument is don't use an off the shelf tool (5 stages) that gets the job done, build your own tool (10 or 3 or none) every time which likely doesn't offer any advantage over the standard tool?
I don't think you really get either Design Thinking or Systems Thinking.
What you are talking about here is not Systems Thinking, which is a particular approach to understanding complex problems by viewing everything as systems of systems. Design Thinking is a methodology for approaching the design process, which is quite orthogonal to whether or not you employ Systems Thinking. The more general field of trying to understand how we determine whether something is true and what it means for it to be true is the field of epistemology; "epistemological based theory" is a meaningless description, like "philosophical based worldview".
I practiced Design Thinking at IDEO for 10 years, and I can assure you it's not "one size fits all." And you can onboard an intern or a client CEO in days, without requiring them to internalize a very abstract system for decomposing problems.
That may possibly explain your motivation but even ten years do not make it right, nor the speed of teaching.
You are saying it yourself: internalising the very abstract system for decomposing and adapting it has a value of its own you cannot replicate by pre-solving it. The spinning-off of Design Thinking only accomplished further segmentation of a space which was already too fractured and was a disservice to the field.
I don’t think we will approach a consensus here, and that’s fine.
It's always valuable to have a generalizable skill. But design is fundamentally a craft; an applied art. It's problem-solving. And like any craft, there are tools and techniques that are tried and true. You could approach woodworking with a ground-up Systems Thinking approach, but would you turn down the advice of a carpenter with 30 years of experience? Technically all you need to understand woodworking is a physics textbook and maybe an organic chemistry textbook.
My guess is you're a software developer (as I am), and in my opinion the fatal flaw of our group is the incorrect belief that we could do anything or solve any problem by simply decomposing it into smaller and smaller components. The thing is, for a big enough problem, there are an almost infinite number of ways to break it down and then build it back up. In optimization terms, complex projects are highly nonlinear problems, so you may be able to understand what the inputs are, but it sometimes takes wisdom and experience to tune the parameters.
Around ten years ago, I was a designer for some 20 years. A strange path led me to a different place which is intermixed or adjacent to the field of organisational theory.
At that time, I decomposed problems too, maybe a bit differently than a developer, I can’t really know. I still decompose, except that the difference to the past is that analysis only makes up one part of the larger whole. I knew many designers which never did either.
I agree with you that there are some areas which do not need theory. That depends on where you define the system boundaries. In the example of a carpenter: Yes, 30 years, the person indeed knows that stuff. One of first question of Systems Thinking, however, would be: What’s the reference system, is his company viable in the future?
I very much believe that if you apply this to complex projects, to ‘communication and control’ of an enterprise, that one should know the backstory.
The reductionist approach got us to the problems, applying reductionism to a theory trying to solve reductionism is courageous. In my opinion, the method which is used to teach must incorporate the principle which it is trying to convey. An alternative worldview needs to have a starting point somewhere, and I like to think it starts with the education, which is not to say that I do not understand the urge to speed up absorption of the theory.
I strongly believe that users will start to demand proof of humanity (and related things like content credentials on photos/videos), and eventually filter out anything that isn't verified. Through great expense and loss of privacy, we will eventually claw our way back to an internet that looks more or less the same as it was in 2020.
Unfortunately, less privileged users will have to endure the sea of AI content that still preys on the unauthenticated. It will be like using the web without an ad blocker, but 1000X worse.
"Commingling" is such a great euphemism for fraudulent counterfeiting.
I can't count the number of times I've ordered a book from Amazon (1st party, Amazon as the seller) and received an obvious counterfeit, with fuzzy text and a poorly printed cover. On one occasion, the scanning/OCR process had missed most of one chapter, so there were just section headers, page numbers and blank pages.
Unfortunately publishers and manufacturers don't have a lot of leverage with Amazon. If there's pressure coming from somewhere, it must be coming from a regulatory body.
This seems like a predictable pendulum swing. I love AI, but I also love the phenomenon of people turning more toward IRL and tangible activities.
Anecdotally, I have friends who have recently bought turntables out of the blue and gotten into vinyl. Other friends who never had any interest in my analog cameras are asking about film. My wife has even switched from scrolling Instagram at night to working on a crossword book with a pencil.
None of them have put it exactly this way, but in divisive times, I think social media is just exhausting. And now you can't even really tell what's real.
The Claude Code model highlights the power of simple search (grep) and selective reads (only reading in excerpts). The only time I vectorize is when I explicitly want to similarity-based searching, but that's actually pretty rare.
Yes, but with LLMs, sometimes simply mentioning the right words is enough to prime the model in the direction you want to take it. If you start a prompt talking about leading and type pairings, it will take greater care with typography. You don't need to be an expert typographer to take advantage of this phenomenon.
How will an LLM "take greater care with typography" if it can't see the page it is creating? How will it "improve" leading if you need a human to see that there's too much distance between lines or too little?
Because humans have already annotated diagrams and examples of what ‘too much’ and ‘too little’ look like, and these have been incorporated into the model. It tries to reproduce the content that is associated with humans indicating that they are taking greater care, and that content has the ‘not too much / not too little’ judgement already baked into it.
reply