Consider a spreadsheet with a field that captures an amount. Instead of the actual amount, the field has a number of interval possibilities, like the ones in the image. What could possibly go wrong?
All database and app design starts with knowing what they are about. What is the purpose, who are the users, which features are needed? In research, the answers are quite specifically shaped by, well, the research and its context. In this post, I will introduce three techniques to answer these questions, and point out why with me you are in good hands.
urtles and their nests is about ten years old or limited in their possibilities. I am considering developing new database software. In this text, I am calling for input from sea turtle NGOs and individual experts about their work practices and for feedback on the outline that comprises the bulk of this text
Variety in data-editors During my work on the SWINNO project and its database I noticed how the assistants who did the data work, I call them data editors, have different strategies of entering data. Also, they know the rules that govern the entry of the variables in various degrees, they have different ways of dealing... Continue Reading →
I ran into the pun 'Weeks of coding can save hours of planning' somewhere on the FileMaker community forum (now the Claris community forum). Found it hilarious! Today, I realized that I have been way too eager to come up with smart solutions for programming problems and started working before searching. It is a type... Continue Reading →
In both research and programming, variables need a name and contrary to what one might think, this is not a trivial thing. The only documentation is the name and perhaps some settings or formatting. I can come up with a minimal set of criteria for the naming of a variable.