So you wanna be a Japanese cook... I'd like to be one!
Several years ago I was invited to Annapolis, MD, by friends from the EP church. There were lots of great happenings, but one of them, a very special evening, took place in a Japanese restaurant. Japanese cooks sometimes present their working process as a special kind of show, not hiding any detail, that is, everything is transparent and visible, and enjoyable!
Sometimes I recall that day when I try to describe my job to non-experts. Producing something nice is just one detail, to show how it was produced, is another challenge. When you commit your code to an open source repository, you have to be prepared that every character of your work should meet high level criteria. And, more importantly, your changes in the source code should be transparent, that is, well visible and clear.
Another level of quality is, in my opinion, to do the planning of the future improvements transparently. In this way your decisions later at the implementation stage will be clear for the others, including newcomers and experienced programmers.
At GeoGebra we try to meet these criteria as much as possible. But in some subprojects there are some restrictions in transparency, sometimes just because of security reasons. This implies that some details cannot be shared publicly. On the other hand, in some of my projects there are no such restrictions at all. One of those projects is geometry theorem proving, and in that project it is more than desirable to share not just the implementation details, but also the basic plans with the community, including not just programmers but theorists as well.
As an important step in the theorem proving project this week a YouTrack site has been published that contains GeoGebra's theorem proving issues. It contains all recent tickets related to the GeoGebra commands Relation, LocusEquation, Prove and ProveDetails. You can read more on them in our Tutorial on Automated Reasoning Tools in GeoGebra.
 |
| A Japanese cook in Sakura, Annapolis |
Another level of quality is, in my opinion, to do the planning of the future improvements transparently. In this way your decisions later at the implementation stage will be clear for the others, including newcomers and experienced programmers.
At GeoGebra we try to meet these criteria as much as possible. But in some subprojects there are some restrictions in transparency, sometimes just because of security reasons. This implies that some details cannot be shared publicly. On the other hand, in some of my projects there are no such restrictions at all. One of those projects is geometry theorem proving, and in that project it is more than desirable to share not just the implementation details, but also the basic plans with the community, including not just programmers but theorists as well.
As an important step in the theorem proving project this week a YouTrack site has been published that contains GeoGebra's theorem proving issues. It contains all recent tickets related to the GeoGebra commands Relation, LocusEquation, Prove and ProveDetails. You can read more on them in our Tutorial on Automated Reasoning Tools in GeoGebra.
Comments