Reviews
We don't usually develop it with C++. I've been interested in open source lately, and I'm looking at a lot of code in C-based for my application, and so I want to understand architecture. I just started reading the book The Great C++I and Architects for 23 years. This book is about the essential methodology and technology to develop and maintain large-scale software systems effectively. The author emphasizes the importance of the developer's software, the structure of the code, the reuse of the
A guidebook for large software projects, C++ I large-scale: Process and Archectectures, Great C+I: Akitssian Geum, Gyp, Gilbot, 2023, is a book dealing with the physical design and composition of a large C+ project based on a multi-scale software development system. It's the composition of a book. Zero chapters explain why reuse of the hierarchy in software development is important, why early engineering is important to increase productivity. Chapter 1 is called Compatur, Ringer, Component, C+,
It deals with the things that should be considered in building a project based on the C+-based. I think it's not bad for C++ developers to read. The design methodology that we're going to introduce is also available in computer languages other than C++, but since the author's example is based on C+, it seems hard to read if you don't know anything about C+. He introduces problems that can arise in creating C++ programs and he also introduces ways to solve those problems. The author gives us a
John Lacos: Large-scale C++ Part I: Procedures and Architecture
Developers study by book. Popular books describe ideal models. They're not actually running a large system. The design of a real giant system that runs close to 30 years of age. Is the code you're writing today a legacy, and the code that you'll write tomorrow a modern one? Is it the legacy code that should disappear when the next generation project comes out? How can we build and grow into software assets instead of changing the consuming code? Developers study by book. I believe in the theoretical method of explaining it in books. But software is complicated. If you were to put a complex reality world into software, ideal theories would collapse. Let's go beyond the theory and learn an architecture that can actually apply to the physical world.
Korean title: 대규모 C++ I편: 절차와 아키텍처
Korean author: 존 레이코스
Korean publisher: 길벗
ISBN-13: 9791140707768
Reviews
We don't usually develop it with C++. I've been interested in open source lately, and I'm looking at a lot of code in C-based for my application, and so I want to understand architecture. I just started reading the book The Great C++I and Architects for 23 years. This book is about the essential methodology and technology to develop and maintain large-scale software systems effectively. The author emphasizes the importance of the developer's software, the structure of the code, the reuse of the
A guidebook for large software projects, C++ I large-scale: Process and Archectectures, Great C+I: Akitssian Geum, Gyp, Gilbot, 2023, is a book dealing with the physical design and composition of a large C+ project based on a multi-scale software development system. It's the composition of a book. Zero chapters explain why reuse of the hierarchy in software development is important, why early engineering is important to increase productivity. Chapter 1 is called Compatur, Ringer, Component, C+,
It deals with the things that should be considered in building a project based on the C+-based. I think it's not bad for C++ developers to read. The design methodology that we're going to introduce is also available in computer languages other than C++, but since the author's example is based on C+, it seems hard to read if you don't know anything about C+. He introduces problems that can arise in creating C++ programs and he also introduces ways to solve those problems. The author gives us a
