Sending birthday greetings

Hi guys

I had been pretty busy these last days, so let me answers the questions addressed to me.

I follow you guys that a codeless solution is welcome. The old school guys here may remember I built the DevToolKit, which helped thousands of users and developers worldwide.

My points are:

• In this article John Hawkins wonderfully explained eventual issues and bottlenecks regarding such OOTB solutions. I'm not saying those solution don't work, but I would like to emphasize that architects and developers may want to make them as standardized as possible, which may introduce some constraints which, eventually, drive to performance degradation. Having that said, some OOTB codeless solutions, depending on the scenario, may be a bazoocam to kill a mosquito.
• There are two type of evangelists: the ones which like to teach how to fish and the ones which like to sell the cooked fish

Best regards

Hi guys

I had been pretty busy these last days, so let me answers the questions addressed to me.

I follow you guys that a codeless solution is welcome. The old school guys here may remember I built the DevToolKit, which helped thousands of users and developers worldwide.

My points are:

• In this article John Hawkins wonderfully explained eventual issues and bottlenecks regarding such OOTB solutions. I'm not saying those solution don't work, but I would like to emphasize that architects and developers may want to make them as standardized as possible, which may introduce some constraints which, eventually, drive to performance degradation. Having that said, some OOTB codeless solutions, depending on the scenario, may be a bazoocam to kill a mosquito.
• There are two type of evangelists: the ones which like to teach how to fish and the ones which like to sell the cooked fish

Best regards

You are right, Andre. We discuss two different paradigms.

• The #1 is to call a professional cook even if you need to get a simple sandwich. And to do it again if you wish to add a salad to this sandwich. And to do it again when ...,  and so on and so on.
  Cons and pros are apparent - not need to worry about cooking, but you have to pay for professional services each time and wait for a professional if they are overburdened.
  
  
• The #2 is to buy the "Food Processor" and be free to cook a wide range of dishes as you wish and when you want. Cons and pros are apparent as well. At least, you should invest money in the tool and some time in learning how to use it, but after that, you save much more time and money.

Paradigm #1 still works well, but programmers become more deficit resource with the permanently rising price in the digital era. Paradigm #2 helps to address this challenge. High-qualified programmers develop no-code tools and open a way to use their knowledge for a wide range of non-programmers in an easy way.

Of course, the no-code tool like Logic Builder is not for qualified Sugar developers like you, Francesca Shiekh, or John Hawkins. But, nobody knows future 

Logic Builder is for application implementation specialists like Thomas Meyerhans-Gülle and Jim Ramlall, or processes experts like Lars Aagesen or Brant Myers. They all are not programmers, but they solve a wide range of tasks that previously relied on developers only.

They use Logic Builder to configure data processing algorithms just as they configure workflows in SugarBPM, calculated fields in Sugar Logic, or a Sugar database customizations in Sugar Studio. It saves time, money and allows to allocate programmers to solve more complicated tasks.

For us, like a Sugar Implementation Partner, it helps to compete with Creatio, Zoho, and Microsoft when they provide their own no-code/low-code tools as their competitive advantage.

Best regards,
Mykola