That was not the lifestyle I was looking for.Īs a solo developer, the last thing I needed was an unhappy customer or some third-party problem that took up precious hours troubleshooting when I was behind already anyway, on top of being late for dinner. Or if not stopping the show completely, it would reschedule it to 5PM on a Friday night, potentially lasting through 2AM on a Saturday morning. Whether it was because OSes had not grown up yet either, or that there was no reliable plug-in distribution method back when my beard was actually ginger, installing plug-ins could sometimes be a real show-stopper. And, of course, the classic scenario where the FileMaker Script Engine (being the shy thing that it is) decided to stop being social and went home from the party early. There were warnings about new FileMaker versions breaking things. There were horrific stories of bugs causing business activity to grind to a halt for hours upon hours. However, in retrospect, the only reason I didn't use plug-ins was because of anecdotal evidence from fellow developers. I landed in the “NO” camp for most of my career.
(2) The veteran often has a strong and immediate knee-jerk reaction to the question, “Should you use plug-ins or should you not?” (1) The veteran is old enough to have paid fees at Blockbuster for returning a VHS tape late. The way I have generally been able to tell a true FileMaker veteran from an up-and-coming developer is simple. That’s what I’d like to address in this post.
Given enough time, Bar Fight Facts can make us blind to good decision making.
0 kommentar(er)
