✳flâneur — a map of the web's best reading

LEAP 71 | PicoGK.org Blog

picogk.org · 3,408 words · saved by 1 readers

Until now, we have talked about programming in general and have understood how to fundamentally structure code. In the last chapter, I gave a very high-level overview, on how you would go about setting up a computational model for a physical object. But I have avoided building geometry so far. This is intentional. Because of the way engineers work today, the object’s appearance, the CAD “drawing”, with all its details, naturally is in the focus. But for a Computational Engineering Model, the logical structure and the flow of information is equally as important. And all the things you learned, about classes, interfaces, constructors, etc. all prepared you for what comes next: Working with PicoGK, the geometry kernel I created in 2023, and which forms the basis for all of our work at LEAP 71. PicoGK stands for Pico (tiny) Geometry Kernel, because it is just that: a shape engine that is intentionally reduced to the max. PicoGK is pronounced “peacock”, as a nod to our feathery companions r

LEAP 71 | PicoGK.org Blog LEAP 71 PicoGK.org /coding for engineers Table of contents First steps in PicoGK Until now, we have talked about programming in general and have understood how to fundamentally structure code. In the last chapter, I gave a very high-level overview, on how you would go about setting up a computational model for a physical object. But I have avoided building geometry so far. This is intentional. Because of the way engineers work today, the object’s appearance, the CAD “drawing”, with all its details, naturally is in the focus. But for a Computational Engineering Model,

Explore this link on the map →

saved by

related reading