HolyGround · Robotics C++ Development System Course
Readable Programming
A C++ development system that doesn't repeat the same style reviews. Take the standards out of people's heads, place them in the repository, and ensure the build enforces those standards.
The same style issues are being pointed out again in the review.
Naming differs from team rules. Errors are thrown as exceptions. Headers that were agreed not to be used are imported. The reviewer explains the reason and fixes the code. When the person changes or an AI generates new code, the same criticisms start all over again.
When there are few files, you can manage by relying on memory. But as the project grows, new team members, yourself from six months ago, and even AI cannot access those memories.
The problem is not a lack of C++ skills. It is because the standards that must be followed exist only in people's heads.
When standards operate within the actual development process, the starting point changes.
Use reviews for design. Instead of repeatedly pointing out formatting and prohibited rules, review the structures and choices that humans should handle.
Integrate AI code into the team. Humans and AI create code under the same documentation and build standards.
Start with product issues. Move into product features on the foundation of units, time, settings, logs, memory, and multi-threading.
Connect coding standards and quality gates to a single repository.
Humans and AI read the same standards, and the build checks the rules that can be repeatedly judged.
Standardize the format. Formatting and static analysis first check the rules that humans used to point out every time.
Verify the behavior. The build stops if the tests run and the coverage fails to meet the criteria.
Leave evidence. API documentation is generated from the code to ensure that the implementation and description do not drift apart.
I have integrated the recurring problems encountered in the field into the development system.
I have worked as a robotics software architect for 9 years. At StradVision, I built Visual SLAM from scratch, applying readable code and industrial standards to the development process, which reduced the feature development period from 2 months to 2 weeks.
At Robotis, due to insufficient ROS performance in a commercial delivery robot project, I built a C++ multi-threading-centered core framework from scratch.
Today, I use a C++ development system every day that connects the judgments gained from this experience into documentation, project skeletons, quality gates, test structures, and foundational layers.
Document the standards and ensure that rules capable of repetitive judgment are checked by the build.
What's included in the course
22 Lectures
It includes 16 sessions on C++ principles, environment, build, quality, testing, and infrastructure layers, along with 6 sessions on AI delegation, documentation, skills, and tool integration.
10 live sessions and recordings
After explaining the principles, I will demonstrate the process of how it operates within an actual system. Even if you cannot attend, recordings will be available for purchasers.
Production Playground for C++
This is a program where reference documents, development environments, build/quality gates, testing, and infrastructure layers are all interconnected. It is provided exclusively to course purchasers.
This is for people like you
Those who develop robotics or autonomous driving C++ projects
Those who refactor AI-generated C++ code to comply with team rules
Those who are managing a growing codebase alone or in a small team
Those who want to create a development system where even the environment and quality standards are reproduced.
Scope and Conditions of Use
This is not an introductory C++ course. You must be able to read and write C++.
The program is not an answer key that allows you to replicate my project exactly. You must exercise judgment and adapt it to fit your own codebase.
It can be used for personal or freelance commercial projects, but redistribution or public disclosure is prohibited. Corporate use requires separate consultation.
Claude Code or Codex account costs are separate.
Conditions to check when purchasing now
The current course price is 1,202,800 KRW. This is the sum of 16 C++ lectures at 50% off the regular price and 6 AI lectures at 30% off the regular price. The total regular price is 2,228,000 KRW.
The course price will change to 1,232,200 KRW starting August 6th. The entire early bird promotion will end once 30 early buyers are reached or on October 8th.
Students can receive an additional discount of 200,000 KRW off the current price, allowing them to purchase for 1,002,800 KRW. The student discount is processed by making a bank transfer and then sending a student ID to yes@holyground.world for verification.
If you already own some of the lectures, the price of those lectures will be deducted from the course price.
When you purchase a course, you own the included lectures for life and will continue to receive updates. Lectures and live sessions added after your purchase are separate.
Instead of reviewing the same style issues over and over, if you want to make the standards actually work
If you have decided to migrate the standards and development environment of your current C++ codebase into an actual system, please check the final conditions on the product page and proceed with your purchase.
Check the final conditions for Readable Programming and purchase
This is an open chat room I operate. If you are curious, please feel free to join and ask questions.