Our Community is Strong
Using broken development frameworks, or why we don’t use Zurmo
The above is the title of a recent blog post about Zurmo that was recently published. It raised some great questions about our application, our community, and the difference between constructive criticism from serious developers and lashing out. Let’s go through that post, step by step.
People often wonder why DBA’s used to hate developers, and with DBA’s also the System Engineers, (note that I just expanded devops by adding dba’s to the picture…)
Hate is such a strong, nasty word. It is appropriately used when describing evil dictators or serial killers.
So let me tell you a story .. A couple of weeks ago one of our customers wanted to start experimenting with a new type of CRM. A gamified CRM. Zurmo …So we set this thing up in a dev environment and started playing with it , while at first it looks nice …
Thanks! We put a lot into the user interface. Glad you like it.
the application actually felt pretty slow.. however given that is a low resource development environment we looked no further. Yet the next step is that we run into missing features, such as the fact that every contact you create by default is set to private .. which really isn’t productive for a CRM system where you want to be able to follow up on different customer and share information.
Good call. You are totally right about that. We decided several months ago that it didn’t make much sense for record visibility to default to owner. So we changed it. It’s a configuration setting that can be adjusted by Admins. You can adjust the default however you want.
Are you sure that your installation was from just a couple of weeks ago?
So we tried figuring out what the database changes to do this in bulk would mean, surely it had to be a flag on the contact record. Wrong, Zurmo uses an ORM for their database connectivity …so their data model wasn’t really trivial.
So we decided to look at the MySQL log file to figure out what db changes happened when updating the record. Yes there’s better approaches but this one learned us a lot .. The procedure I followed was pointing my browser to the page where I wanted to switch the checkbox, log on to the mysql box, set global logging on. Clicked the checkbox and stopped global logging. This gave me a log file with all the database actions required to make that one single change. I had to cross check a number of times … the file created by this short and small action was about 70K
Yikes! Response from our lead engineer, “He definitely shouldn’t be getting 70k for creating or updating a contact record, so maybe he has some sort of environmental issue or something else is going on. Maybe he has debug=true and he’s not running memcache, but either way 70k is way too high even for that. It would be great to know what happened to cause that. Has he posted on the forums?”
We are guessing he is talking about using the designer tool and making a change to a field via designer. This issue with queries is being addressed here: https://www.pivotaltracker.com/story/show/50389649.
It’s kind of hard to know what the real issue is, however, unless if we can see a real world example. It would be nice if this issue could be posted in the forums so we can get to the bottom of it. That’s how open source communities work.
Puzzled you start looking at the queries … The query list was full with “SELECT * FROM ” stanza’s .. 70K whopping K of queries that make your hair turn grey …
Grey hair is no good. Life is too short. Some people try yoga. For others, going to the gym does the trick. Maybe a walk in the park to get a bit of sunshine.
I figured I’d file a bug .. but I couldn’t find no [sic] bugtracker for Zurmo, only a forum (and forums are the most broken form of communication imvho)
Oops! It looks like you didn’t see our bug report. It easily accessible link on zurmo.org under development ->report a bug. https://bitbucket.org/zurmo/zurmo/issues
…yet the developers responded on Twitter.
That is correct. We did respond on Twitter (see below). We prefer it when people ask questions through the proper channels. But of course, if we see a tweet about us, we’ll usually respond.
The feedback wasn’t really satisfying so we quickly decided that supporting this application was not something we would like to do.. and abandonned it.. The real question is who needs a Gamified CRM anyhow…
That’s a great question. So far, from the number of people downloading Zurmo everyday, engaging with us through the forums, and giving us positive feedback, quite a few.
We’ve put about three years into Zurmo. 99.99% of all people who come across it have responded positively. Or at least their criticism has been constructive. Hate, on the other hand, is an entirely different kind of animal.
We know the author/reviewer is busy. Probably too busy to respond to this. But if he does have something productive and non hateful to say, he should feel free to submit a forum post where our community can respond in a useful way. We also have weekly dev sessions that he is more than welcome to attend. And once again, bugs are reported under “Development” in our main menu.
Moral of the story: We don’t believe Twitter is the place to support the intricacies of a sophisticated CRM system. Our community helps one another in our forums. We do have a proper channel for bug reporting, and we won’t be bullied.
*Let’s review those Tweets: