Starting with FileMaker in 2021
By Seppe Van Praet.
How FileMaker gained my interest
I learned about FileMaker in 2020, quite a few years after its initial release in 1985. A close friend mentioned he had started developing a FileMaker app. Initially, it didn’t pique my interest all that much. Still, in college, my focus was on programs such as Unreal Engine, Unity, and 3D Studio Max. Databasing software, not so much.
A year later, after leaving college, I started looking for possible job opportunities. The same friend that introduced me to FileMaker, had been working for a company called ClickWorks. Who specialized in FileMaker development. After he heard I was looking for a job, preferably one that didn’t involve the fast-food chain McDonald’s, he mentioned that the company he was working for needed new FileMaker developers. My interest in FileMaker grew slightly at the possibility of employment. We got to talking about FileMaker, the company, and the apps he had been developing. A couple of hours and some demos later, my interest in FileMaker had grown significantly.
The next morning, I downloaded the free trial for FileMaker 19 and got to exploring. I started working my way through the FileMaker training series and making small projects, such as an app to store data on movies I’d seen.
Like most development software, it took some time to get used to the ins and outs of the program. While a lot of my programming experience came in handy, the differences between FileMaker and developing in c++ or making a game in UE were rather large. But once I knew my way around the relationship graph and the script editor, it was easy enough to quickly turn my concepts into a working application.
After messing around for a month with the program, I managed to land a “free-lance” FileMaker job. I had to recreate an existing app from the ground up, adding in some functionality and tweaking some features. It took me some time to get into it, seeing as it was quite a step up from the tiny projects I made before. But after some time, I had most of the basics figured out and enough knowledge to solve most of the problems I encountered (or at least enough know-how to understand the things I copied from the Claris community). Things went smoothly.
How I finally ended up at ClickWorks
Meanwhile, at the ClickWorks office, they received a mail with a not all that impressive CV. But with a convincing recommendation from my friend who worked there, they agreed to have me come over for an interview. On the condition, I could work out a small assignment they gave to every applicant. Which was not all that challenging with the experience I had already gathered over the last few weeks.
So, I sent in the assignment, with some extra work to show my eagerness and a week later stood at their doorstep for an interview. Sweating profusely because of the summer heat and the fact that I had never done a formal interview before I rang their doorbell. Jeroen and Joris were very welcoming if a bit skeptical at the start of the interview. To explain their skepticism: I was young, switched bachelors three times before dropping out of college after 4 years, and had very little to show for it except some knowledge of zoology, c++ programming, and 3D modeling. None of those were very useful for the job I was applying to. But after going over the assignment and some other things I had built in FileMaker they quickly opened up to the idea of hiring me for an internship.
The first week was a tad confusing, figuring out how the company ran and my role in it took some getting used to. Let alone trying to understand some of the monstrous projects they were developing. But with time (and a great deal of help from my colleagues) comes understanding. For the first few weeks, my assignments were clearly defined and thought through by Jeroen or one of my colleagues. Unfortunately, no developer is safe from unexpected behavior or the complexity of an application. More than once I jumped down the rabbit hole until I found where the issue was hiding, usually after spending an hour of intense staring at the script debugger. Luckily mistakes and frustration can be great learning tools, it’s hard to forget something when you spent an hour looking for it.