We invite everybody to make a short (5min) micro-presentation showing off something that is either very useful for them or that has captures their imagination.
Not everybody is used to speak in front of a group, but that is exactly what Vienna Calling is about. So this is an icebreaker of sorts. It is also a hook to get in touch with the other attendees more easily.
Please just open a file, zoom in and show and tell!
Strategies, Costs, and Long-Term Relationships Ensuring the sustainability of FileMaker solutions from the perspective of a development company requires a thoughtful and strategic approach. Beyond the initial delivery, a system’s success hinges on its ability to adapt and evolve. This discussion will focus on key variables for budgeting maintenance, fostering strong and mutually beneficial client relationships, and ensuring the technical and financial sustainability of projects over the long term.
Brief introduction to Initiative '24 (24U's endeavor to make the FileMaker calculation engine significantly faster for everyone), followed by a discussion on details like:
why and how it can be done
why it's worth the effort and why it makes sense along with other great improvements
how to convince Claris to make it priority (i.e. how to get enough votes to make it idea #1)
how to help Claris to get it done
how to benchmark and which functions to focus on primarily
how not to break any existing solutions but still make all of them faster
Most of you already know about this initiative, so I want to keep the introduction very short and instead focus on joining our forces to come up with solid strategy that makes sense and has a chance to get accepted and adopted by Claris.
In this hands-on session, I'll explain how to generate more efficient code, optimize scripts, and speed up your workflow with the help of AI. I'll show real-world examples, best practices, and techniques that you can immediately implement in your projects. Ideal for Filemaker developers who want to boost their productivity and take their skills to the next level using AI. You don't need to be an expert to generate good code.
### Thinking fast and slow somebody said. In what narrative I thought.
The thinking of data as your thoughts; turning into IP( Intellectual Property )
What is backup? rsync to the cloud? Does your term backup have a definition? Does a media have to be physically distanced to become a backup? Such as an ejected LTO or CDVD/BD-ROM?
Defining these terms are imperative to defining who you are in the digital world.
Do you have seeding strategies for your laptops and workstations?
## Your thoughts can have different forms and iterations * In your mind * Written down on paper * Written down in your computer * Structured * SOP? Standard operating Procedure; what most apps should be based on? * Computer application solution; FileMaker, iOS, web, and / or others * Live data from computer, searches in database * Published from live data, as pr example SSPR( Server Side PreRendered ) as dead HTML, to offload database, and for SEO to index more quickly.
I'm not saying these are the right sequence for your thoughts, I'm saying that these should be considered and maybe be a starting point for your very own thoughts.
As markdown: https://gist.github.com/TyrfingMjolnir/4b7c63ca1bce6780d30948183a861698
Day 2
14:00-15:00
Mezzanin - Breakout (14 seats)
Gjermund Gusland Thorsen
Day 2 | 14:00-15:00 | Mezzanin - Breakout (14 seats)
Sharing and explaining cool and complex calculations, (such as those in my examples PDF Links, PDF Barcodes, PDF Canvas, PDF Pages, PNG Barcodes, PNG Canvas or Advent of Code), discussing different approaches to creating, debugging and optimizing calculations, when (not) to use the help of AI, what challenges we have faced and how we dealt with them etc.
Intentionally setting this to a small room in parallel to the MBS session, this is primarily intended for people who prefer (for whatever reasons) pure FileMaker calculations even for complex tasks over leveraging plug-ins, JavaScript and other alternatives. I can imagine 1 hour may become too short even in a very small group of people... ;-)