One year of R&D: what the work taught us
Looking back at the first year of our FFG Basisprogramm project, the contrast between difficult problems and apparently simple tasks stands out.
Looking back at the decisions
By September, a lot of work was behind us in our FFG Basisprogramm project. Reports, validation and budgets gave me a reason to pause and look back. The useful part was remembering how we had reached the decisions, not just listing what had happened.
I could see ideas that worked well and choices that deserved another look. Some of our most complicated technical problems were solved as planned, or even faster. Some things that had looked easier slowed us down.
That contrast is the point I wanted to share in my original post. An early estimate does not tell the whole story of a task. We need to pay attention to what the work itself teaches us.
Several parts have to move together
Our research direction brings together geometry, slicing strategies, interface work and validation. A change in one area can affect the work in another. Getting a component to work is therefore different from having a clear workflow around it.
The model has to be represented in a useful way. A strategy has to work with that representation and produce paths a person can inspect. The interface then has to make those choices understandable.
This connection between parts is also why finishing and testing matter. It is easy to describe a feature in a few words. It takes more work to understand how it behaves within the rest of the software.
The people behind the progress
As the year developed, we also introduced new colleagues and shared more of the product work publicly. Our summer private-access announcement for Toolpath Editor was one concrete point along that path. It gave us a way to explain a focused workflow around existing machine code.
Looking back, I think about the people who made these steps possible. The team’s work includes research, implementation, review and the many discussions needed to connect them. Those contributions do not all fit into a short progress list.
The lesson for our next stage is to keep looking at the whole job, including the parts that initially seem straightforward. We are growing and learning through the work. I am proud of the team and everyone who has contributed to this first year.