Forum Discussion
_anomDiebolt_
8 years agoQrew Elite
Some of you items need additional clarification but in general I don't see anything on your list that cannot be implemented by a user using script.
MB> ...for some of the good ideas, it can take 5 to 10 years
With script you can implement new ideas in as little as 5 to 10 minutes. Any web related idea that takes 5 to 10 years to land is due to not trying very hard or at all.
MB> ...for some of the good ideas, it can take 5 to 10 years
With script you can implement new ideas in as little as 5 to 10 minutes. Any web related idea that takes 5 to 10 years to land is due to not trying very hard or at all.
MichaelBarrow
8 years agoQrew Cadet
I work for a small business, and I am the single resource for creating and supporting our QB app on which we run our entire company. The big issue for small business is cost. Not just direct costs but all costs. Above all, the skill that affords the highest degree of success in my environment is pragmatism. I weigh all the costs of every decision I make, not just how much time it will take me to bang out a working app today. Having said that, I don't want to reinvent the wheel. I'd rather pay QB a nominal monthly fee to do the heavy lifting for me. If I wanted to lift heavily, I'd be working as a coder. I've done that for decades, but I'm tired of that and I just want to focus on making my business better and more profitable. As such, I think I am a very typical QB customer. The overhead costs of supporting code are staggering compared to the effort to create it. That is why I avoid it as a first choice for anything. QB helps me do that most of the time. I am addicted to the speed at which I can implement changes in our business processes on the QB platform without code. As soon as I think I need code for something, it causes me to pause and thoughtfully ask myself if it really is necessary.
Formulas in QB are very well encapsulated and quite different from Javascript which needs to bring in and reference different external libraries from different sources that will change to different version numbers and potentially break things as QB iterates its environment. I have purchased well-developed 3rd party code that has already broken, not due to anything the programmer did wrong but due to QB making changes that no longer played nice with the old code. That's complexity, and you don't get that when writing formulas directly in QB.
I'm not against code, but I am definitely against unnecessary complexity. As Joseph Tainter pointed out with regard to society and civilizations, complex systems tend to fail catastrophically. Same goes for applications. I've watched so many applications fail over the years due to being designed and implemented in overly-complex ways that usually involve way too much code. I'm not being an ideologue, I'm just trying to be pragmatic ... and profitable for the long-haul.
Formulas in QB are very well encapsulated and quite different from Javascript which needs to bring in and reference different external libraries from different sources that will change to different version numbers and potentially break things as QB iterates its environment. I have purchased well-developed 3rd party code that has already broken, not due to anything the programmer did wrong but due to QB making changes that no longer played nice with the old code. That's complexity, and you don't get that when writing formulas directly in QB.
I'm not against code, but I am definitely against unnecessary complexity. As Joseph Tainter pointed out with regard to society and civilizations, complex systems tend to fail catastrophically. Same goes for applications. I've watched so many applications fail over the years due to being designed and implemented in overly-complex ways that usually involve way too much code. I'm not being an ideologue, I'm just trying to be pragmatic ... and profitable for the long-haul.