Over years of reviewing Ruby code, the same things tend to come up over and over. In this post, I’d like to address some of the most common code smells I find when reviewing OOP code (and Ruby code in particular).
Doing the simple is hard. Someone recently reminded me of this when discussing business workflow. Tasks like scheduling, calendaring, communicating and sending notifications are individually manageable, in a world where tools for these tasks exist online. Calendars, email, databases, Slack, and a collection of other apps and services make this possible.
Combining functions, features, or steps in creative new ways can deliver productive results. I was thrilled to discover in FileMaker 18 that the new file-based script steps give us the ability to perform imports natively on FileMaker Server, with no configuration or changes needed.
Well, here we are again! With the release of FileMaker 18 we get the third version of the FileMaker Data API. This version brings an iterative advancement in features while maintaining the core functionality that was introduced with V1 of the API in FileMaker Server 17.
This story started when we explored iOS Shortcuts to the FileMaker Data API. As we continue to automate tasks by mixing together iOS apps, content on mobile devices and web APIs plus FileMaker, let’s add to our workflow using one of the most powerful functions available to iPhone and iPad users: Siri.
Once you have crafted a Tableau dashboard, pulling data from your FileMaker solution, then your next goal might be to make sure the dashboard data gets refreshed at regular intervals, and in an efficient manner. And that is what we’ll do in this blog post.
We have better tools than ever in FileMaker to create reusable modules. In this video of Mark Scott’s presentation at a Bay Area FileMaker developer meetup, he explores why the combination of card windows and JSON reigns supreme for modular FileMaker architecture. Included is an in-depth look at how modules can open, close, and communicate.
“Code that belongs”. This is the mantra, the quest, of Beezwax Senior Developer Ryan Simms; which he discusses in this ten-part article on building a large-scale web application using d3.js. How to write code that fits the context intrinsically. The article focuses on specific techniques with the data visualization library, d3.js. But the lessons are broad. How do you make something fit — in ways that make it feel like it belongs?
When I am working in the Bay Area, I often carpool to Beezwax’s Cupertino and Oakland offices with Vince Menanno, the creator and lead architect of InspectorPro. Over two years of commuting, I have been bugging him to add global search to InspectorPro, so FileMaker developers can search elements across the entire DDR for any solution. Vince must have gotten tired of my nagging, because at long last we can all enjoy this functionality, in InspectorPro 7.
Dear InspectorPro: Can you show me a report on the container fields used in my FileMaker solution, with a list of all externally-referenced vs. internally-stored (“embedded”) fields? Sincerely, Thanks in Advance-d.
Hello again from Tableau Conference 2019 in sunny Las Vegas! Here at Beezwax, we had 5 attendees this year with a diverse set of sessions between us. I wanted to give a rundown of what I went through and some of my takeaways.
Recently I was tasked with implementing a picker list whereby the user could assign people to a project, and indicate each person’s hourly allocation to that project as that assignment was made. How can data be associated with names in a picker list, before those names have actually been stamped onto their own records?