Bookshelf

I studied computer networks at university and started my career in software development. Manufacturing systems taught me programming and on-premises fundamentals; an Enterprise Architecture team taught me to optimize a whole company, not a single system. From there: a B2C e-commerce site, cloud data platforms, and requirements definition on the business side of advertising. I never changed employers — it just turned out that way.

Every time my position changed, the same thing looked different. A cone is a circle from above and a triangle from the side — both views are correct. Business talks in revenue and customers; systems talk in data and latency. Same object, different words. Each time the person I worked for changed, I had to switch how I think and how I speak.

To switch well, I leaned on books that teach systematically — certification study included. This shelf holds only the books I genuinely found worth reading. Growing the count is not the point. Trust comes less from what is said than from who says it; recommending a good book is an extension of that trust.

From networks to systems, architecture, cloud, data, and business. Less a series of career changes than a viewpoint that kept widening.

The shelves are organized by who I was working for.

• 9.1BusinessFor BusinessFor strategy, marketing, and the bottom line
• 9.2CustomersFor CustomersFor users, requirements, and UX
• 9.3ProjectsFor ProjectsFor delivery and teams
• 9.4SystemsFor SystemsFor design, development, and operations — incl. Practical Monitoring
• 9.9CareerFor CareerFor my own learning — certifications as a starting line