Alec Gregory from Beezwax presents at the Claris Beyond Meetup.
Alec Gregory from Beezwax presents at DIGFM & Bay Area FileMaker Developer Meetup.
When it comes to choosing web development technologies, we now have more options than ever. And while that’s a good thing, it also poses a problem. Answering the question, “What is the ideal technology for this new project?” is not as easy as it used to be. In this post, I briefly highlight the most popular full-stack web frameworks, and why you might want to choose each of them.Continue reading “Modern Full-Stack Web Frameworks: When to use What and Why”
Vincenzo Menanno and Fabio Bosisio from Beezwax present at Rome FileMaker Week.
This week we’re in Italy… formazione, condivisione e ancora divertimento [training, sharing and more fun] …with the focus on innovations in Claris® FileMaker platform development. As realtori [conference speakers] at Rome FileMaker Week (October 6-8), Vince Menanno and Fabio Bosisio from Beezwax present three sessions:
- Local FileMaker Development with Docker and Node-RED
- The New Horizon: Native Script Transactions in FileMaker
We are pleased to release bBox version 0.99 for Claris® FileMaker® on macOS and Linux with new NodeJS and Python 3 integration, and M1 Apple silicon support for GraphicsMagick image processing and JQ JSON parsing functions.
About bBox Plug-in For FileMaker
bBox is available on macOS and Linux, and runs with either FileMaker Pro or FileMaker Server. Here’s what FileMaker Magazine had to say about bBox version 0.99:
Software changes over time. Your company’s web site this year does things you had no idea you needed two years ago. How can we keep the cost of change manageable?
Automated testing is one way. Especially for large software projects, the practice of automated testing can dramatically reduce the cost of adapting software to new business necessities.
There are entire books written on testing. And it surely feels more an art than a science. My approach is similar to Kent Beck’s:
I get paid for code that works, not for tests, so my philosophy is to test as little as possible to reach a given level of confidence (I suspect this level of confidence is high compared to industry standards, but that could just be hubris). If I don’t typically make a kind of mistake (like setting the wrong variables in a constructor), I don’t test for it. I do tend to make sense of test errors, so I’m extra careful when I have logic with complicated conditionals. When coding on a team, I modify my strategy to carefully test code that we, collectively, tend to get wrong.https://stackoverflow.com/a/153565/1015566
He goes on to add that different people will have different strategies and, at the end of the day, you just have to do what works best for you and your team. Extremely practical, and the approach I personally follow.
This won’t be a detailed post on every possible topic on tests and testing in Object-oriented Programming (OOP). There are many books about that already. Instead, this article will cover the basics of testing, so you understand how and why we test, and you can adapt it to your own needs.Continue reading “OOP Fundamentals: Quick and Dirty Guide to Testing”
The decorator pattern is one of my favorite patterns. It is simple, extensible and powerful. It feels like it follows the essence of object oriented programming beautifully. Sadly though, it is also easy to be misused or misunderstood. So, in this post I will show you the essence of the decorator pattern, illustrated with a few examples.Continue reading “OOP Fundamentals: The Decorator Pattern”
The dependency inversion principle is one of the cornerstones of object-oriented programming. Without it, there is no object-oriented design. It’s that important.Continue reading “OOP Fundamentals: The Dependency Inversion Principle”
Using the FileMaker platform we can harness the power and wow-factor of modern web interfaces. This post shows how we can build dynamic data-entry forms for use in our apps.
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).Continue reading “Common Code Smells in OOP”
As developers, we are tasked with reducing complexity. Complexity is all around us, and good code organization reduces complexity while at the same time supporting increased flexibility, ease of change, quicker onboarding, faster debugging, and my favorite, better testing.