Name the assumption
We start by writing down the belief as plainly as a reader might hold it, without softening it into something easier to argue against. If we cannot state the myth fairly, we do not publish the correction.
Correcting assumptions about information models, one myth at a time
Generationrich is a small editorial project that explains how models of information processes actually work, by naming the common misconception first and the calmer reality second.
Why this site exists
Most explanations of information processing start from the assumption that the reader already believes something wrong. A diagram gets called a system. A flowchart gets treated as proof of how data truly moves. Generationrich exists to slow that down and look at what a model is actually claiming, and what it quietly leaves out.
We noticed that the words collection, processing, storage and transmission get used loosely in everyday conversation, often carrying more certainty than the underlying model deserves. This site was built to separate the two: the model as a simplified representation, and the popular belief about what that representation guarantees.
How the material is produced
Each page starts with a list of things people commonly assume about a stage of an information process, gathered from general reading, forum questions and everyday conversation rather than from any single source. Those assumptions are checked against how the concept is actually defined and used in introductory computing and information science material.
Writing is done in plain English on purpose. Technical precision matters, but so does a reader being able to finish a paragraph without a glossary open in another tab. Where a claim cannot be simplified without becoming misleading, we say so directly instead of smoothing it over.
Who is behind it
Generationrich is maintained by an independent editorial team with a background in technical writing and computing education. There is no single named author presented as an authority; the site is a collective effort to keep the explanations accurate, current and free of jargon that hides more than it reveals.
We do not represent a software vendor, a data broker or a consultancy. Nothing here is written to make a product, service or company look more capable than it is, because nothing here is selling one.
What this site is not
This is not a technical standard, a certification body or a substitute for a proper course in computer science or information systems. It does not offer personalised advice about any specific system, device or organisation, and it does not claim that reading it will produce any particular outcome.
Where a topic is genuinely contested or where practice varies by context, we say that plainly rather than picking a side for the sake of a tidy answer.
Editorial method
Myth first, then the calmer explanation
Every article on Generationrich follows the same shape. We state a belief that is common but imprecise, then explain what a model of that process is actually built to do, and where its boundaries sit. This is not done to catch anyone out; it reflects how most people are first introduced to these ideas, often through metaphors that were never meant to be taken literally.
The aim is calibration rather than correction for its own sake. A model that collects, stores or transmits information is a deliberate simplification of something more complicated, and simplifications are useful precisely because they leave things out. Understanding what has been left out is, in our view, more useful than memorising a diagram.
How we work
The checks every article goes through
Consistency matters more to us than speed, so each piece passes through the same set of questions before publication.
Check against the fundamentals
Every claim about a stage of an information process is compared against how that stage is described in general introductory material, not against a single opinion or a single product's marketing.
Rewrite for clarity
A correction that is more confusing than the myth it replaces has failed. We rewrite until a reader with no technical background could follow the reasoning from start to finish.
Flag genuine disagreement
Some questions about modelling do not have a single settled answer. Where that is true, the article says so, rather than presenting one convention as the only correct one.
Ground rules
What guides every page we publish
- Neutral by design
- We describe how models work in general, not how any particular company's system is built or marketed. No page is written to favour a product.
- No outcome promises
- Understanding a model better does not guarantee a particular result in any real project. We never suggest otherwise.
- Limitations stated openly
- Every model leaves something out. We treat naming those omissions as part of explaining the model, not as an afterthought.
- Plain language first
- Jargon is introduced only when it adds precision, and always with a plain-English explanation alongside it.
Questions we get asked
About this project
Is Generationrich affiliated with any software company or vendor?
No. We are an independent editorial project. We do not accept sponsorship to favour a particular product, and no page on this site recommends or reviews a specific commercial tool.
Does this site teach me how to build a real information system?
Not directly. The focus here is on how models of information processes are conceived and where common beliefs about them go wrong. It is a companion to formal study, not a replacement for it.
Why focus on myths instead of just explaining the topic normally?
Because most readers arrive already holding an assumption, often absorbed from a metaphor or a simplified diagram. Naming that assumption first tends to make the correct explanation land more clearly than starting from a blank page would.
Who reviews the content before it is published?
Articles are drafted and checked internally by our editorial team against general introductory material in computing and information science before publication. We do not name individual reviewers, since the site speaks as a collective effort rather than through a single byline.
Will the site ever cover a specific product or brand in depth?
Our intent is to stay at the level of general concepts. Naming a specific brand tends to date an article quickly and shifts attention away from the underlying idea, which is the opposite of what we are trying to do.
Continue reading
Related pages on this site
Read the fundamentals before the myths
If this is your first visit, the clearest starting point is the page that lays out what an information model actually claims to do, before working through the individual misconceptions.