3 ms·

I dont think it's quite so simple. Maybe 70% of business problems fall into a camp that no code tools can deal with and a long tail of 30% that do not. The pro

by pydry 4y ago

I dont think it's quite so simple. Maybe 70% of business problems fall into a camp that no code tools can deal with and a long tail of 30% that do not. The problem is that: A) No code tools rarely provide good guidance as to where that 70/30 split lies. B) It often takes a good coder to figure out when you've run into this square peg round hole problem and if you use a NCT you probably dont have one to hand and non technical users are SO bad at this (they will often think that they are the problem). C) No code tools often end up reinventing programming languages really badly to bridge that gap instead of bridging like they should in an effort to keep users on their platform and because designing programming languages badly is fun! D) As a result, most people not only misrecognize that 30% long tail and misapply the solution. As a result no code tools have a perpetual allure until they get used on slightly too complex a problem at which point they become uber brittle and everybody starts tearing their hair out. Sometimes the rigidity of the no code tool is baked in, which is even worse (e.g. like this one's bad mobile UX).

danielvaughn 4y ago
This is a great response, I agree. One thing I'll add onto point A is that I think it's sometimes impossible to know which side of the 70/30 you're on until the rubber has hit the road and you're deep into implementation. Which of course, complicates the whole thing even further. Take this recent experience of mine - I'm helping someone build a teletech system with Twilio. Nothing too crazy, just connecting customers to a service provider. Seems like the perfect candidate for NCT - heck, even Twilio offers their own in-house NCT (Twilio Studio). I just started building it yesterday and a literal avalanche of questions hit me. What if the call drops? What if the customer isn't happy with the service and wants to speak to someone else? What about (x/y/z) concerns? Before beginning I would have put this project square in the 70%, but now I'm convinced we're in the 30%.

by pydry 4y ago

danielvaughn 4y ago

This is a great response, I agree. One thing I'll add onto point A is that I think it's sometimes impossible to know which side of the 70/30 you're on until the rubber has hit the road and you're deep into implementation. Which of course, complicates the whole thing even further. Take this recent experience of mine - I'm helping someone build a teletech system with Twilio. Nothing too crazy, just connecting customers to a service provider. Seems like the perfect candidate for NCT - heck, even Twilio offers their own in-house NCT (Twilio Studio). I just started building it yesterday and a literal avalanche of questions hit me. What if the call drops? What if the customer isn't happy with the service and wants to speak to someone else? What about (x/y/z) concerns? Before beginning I would have put this project square in the 70%, but now I'm convinced we're in the 30%.