# The industry, from inside: six articles on how this business actually works > Who founds the companies, how a product travels from the people who build it to the people who depend on it, what the role in the middle of that path does all day, what a customer is really buying when they buy transformation, and what every appliance on the estate is running underneath. Six articles that are not about any vendor, read in the order a career meets them. Source: https://ronutz.com/en/learn/the-industry-from-inside Updated: 2026-09-09 --- ## Why these belong together Most of this catalogue is about how a technology works. These six are about how the *business* around it works - the shape that stays the same while the products change - and they are the articles a practitioner tends not to look for, because nobody is tested on them. They are read here in the order a career encounters them: first the population that starts the companies, then the path their products take, then the role that sits in the middle of that path, then what the customer at the end of it thinks they are buying, and finally the thing all of it runs on. ## 1. The people are the constant **[The founders who kept founding](https://ronutz.com/en/learn/the-founders-who-kept-founding)** - the observation is James Pelkey's: the field is an entrepreneurial *population* recombining, not a sequence of firms. Ungermann left Intel for Zilog and Zilog for the first company whose whole business was networking; Metcalfe left the lab where Ethernet was invented to found 3Com. The pattern explains why companies arrive in clusters, why competitors share architectural instincts, and why an acquisition is usually the start of somebody's second company. It also has a trap, and the article names it: a history told through the people who moved makes invisible the people who stayed and built most of what got built. ## 2. The path a product travels **[The path a product takes](https://ronutz.com/en/learn/the-path-a-product-takes)** - between the company that builds a thing and the person who depends on it, the product passes through many hands, and each pair belongs to a job with its own clients, suppliers and accountabilities. This is the map that makes sense of the vendor chapters elsewhere on the site: the same product looks different from the factory, the distributor, the reseller and the customer, and a great many misunderstandings are two of those looking at the same object. ## 3. The role in the middle **[What a channel systems engineer does](https://ronutz.com/en/learn/what-a-channel-systems-engineer-does)** - inside a distributor there is a role almost nobody outside the channel can describe: the engineer who supports resellers rather than customers. Bill-of-materials work, proof-of-concept execution, partner enablement, and the escalations that arrive when a reseller's own engineer has run out. It is the job that sits at the exact midpoint of the previous article's path, and the description is written from inside it. ## 4. What the customer thinks they are buying **[Digital transformation](https://ronutz.com/en/learn/digital-transformation)** - the phrase on every deck, examined honestly: transformation is not the technology arriving, it is the moment a capability stops being remarkable and becomes assumed. The article walks what genuinely changed across money, work, health and the rest, and is the antidote to the version of the term that means "we bought something." ## 5. What all of it runs on **[Unix and the appliance you operate](https://ronutz.com/en/learn/unix-and-the-appliance-you-operate)** - log into a load balancer, a firewall or an access point and look underneath the management interface: a filesystem, a shell, syslog, cron, tcpdump. The appliance is a Unix system with a product on top, and the article traces how a 1956 antitrust decree produced, as a side effect, the distribution model the whole industry runs on. Its practical rule is the one to keep: reading from the shell to diagnose is normal; writing to it to fix things is how estates become unsupportable. **[What grew out of Linux](https://ronutz.com/en/learn/what-grew-out-of-linux)** - Android, ChromeOS, the container industry, the build inside the car, the firmware in the router. All Linux, in very different ways, and the interesting question is what each one kept and what it discarded. Read with the previous article: between them they are the substrate under nearly every device in the estate. ## What the set says together The technology in this catalogue changes every few years. These six describe the things that do not: the same population starts the companies, the same path carries the products, the same role translates between the layers, the customer is buying the same thing under a new name, and it all runs on the same operating system lineage it ran on forty years ago. A practitioner who knows the shape is not surprised by the next wave, because - as the first article puts it - a technology arriving claiming to be unprecedented rarely is. For the vendor-by-vendor version of this history, see the [career chapters](https://ronutz.com/en/industry/chapters); for the technology lineages, the family histories on the [industry page](https://ronutz.com/en/industry).