After spending two days writing a calculation function, I figured I wasn’t a day short, and that sharing the story behind writing this function could be interesting for other developers—not so much for the function itself, but to capture the mindset and the general ideas that help approach a complex function.
Moreover, since Claris has honored me with a spot at the Engage conference next March in Austin, with a topic as unusual and pretentious as “how I, Fabrice Nordmann, tackle a problem to solve with the FileMaker platform,” I need to start seriously reflecting to understand my own process in order to explain it. As readers, you’re serving as my test audience, for which I thank you.
Nice blog post. Nice CF.
Nice clear CF structure.
I’m not hot on all the one letter variables, … for a newcomer to the CF it makes it difficult to digest.
I see you are using lowerCamelCase for your json keys. I prefer lower_snake_case – because the complete abolition of capital letters removes the ambiguity of how to code acronyms such as ‘ID’. The ‘id of a person record’ in lower_snake_case is unambiguously ‘person_id’, whereas in lowerSnakeCase it could be ‘personId’ or ‘personID’, depending on what dialect of lowerSnakeCase you are using.
I have a similar JSON for performing a FileMaker find. It’d be interesting to see how similar/different they are.
Glad you are enjoying my [+] and [:] syntax! 😀
…and I LOVE IT when your brain starts buzzing and things start ‘going sideways’!
…looking forward to part 2!
See you at EngageU
<3 MrWatson