Published on 27 June 2014 by @mathiasverraes
You are reading this on an Information Overload Device. Probably one that fits in your bag or even your pocket. You also have a large Information Overload Device in your living room, and there’s a bunch of others spread across your home, your office, and your environment.
The way humans deals with information overload, is to scan quickly, and put everything in buckets. We find the similarities with ideas we already know, and then categorize it under the same name. It’s a database that stores entire documents? Oh, then it’s a document database, like the document database I already know about. It has small iterations? It’s an agile methodology like Scrum. It uses the language of the business? It’s like BDD. You get the picture. Categorizing information is often a necessary strategy.
We do so much of the “scan, bucket, repeat”-cycles, that we forget to actually process interesting information. My method is simply this:
The divergence, the conflicts, the raison d’être’s, that is where the learning happens.
(Post intentionally kept short to prevent information overload).
Follow @mathiasverraes on Twitter.
|Advanced Domain-Driven Design||DDD Europe||workshop||Brussels, Paris||2018|
|Design Heuristics||DDD eXchange||keynote||London||April 2018|
|DDD for Messaging Architectures||ExploreDDD||workshop||Denver||Sep 2018|
|Design Heuristics||Kandddinsky||talk||Berlin||Oct 2018|
|Tactical DDD||Kandddinsky||workshop||Berlin||Oct 2018|
This work by Mathias Verraes is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 License.