Acquisition Widget Road-Map

Quin-C Development

I hate, hate, hate roadmaps. They are definitely not your traditional win/win. In fact they are more like lose/lose/lose. Customers lose because they don’t fully understand, overlay their own expectations and get frustrated if those expectations aren’t met. Product management and employees lose because they go ahead and make commitments based on the roadmap and then changes or delays cause them great pain. Development loses because pressure is created were there need be none, they are prevented from following the most intelligent path because they only discover it as a function of the development process, and finally everyone blames them for all the pain suffered. The common theme to all this trauma is the face that roadmaps convey far more certainty then can be delivered. That said, my desire to be as open book as possible overrides these other concerns, so against my better judgment I am going to try to layout the roadmap for the acquisition widget in Quin-C. For simplicity sake we will divide this discussion into three parts. Near-term, meaning the next three months, medium term, meaning within the next 9 months, and long-term, which means everything farther out than 9 months. From a risk perspective it is the medium term group that is most likely to be meaningfully wrong so keep that in mind as you read.

Read More

tleehealey | Thursday 01 November 2018 - 06:21 am | | Default | No comments
Used tags: , ,

Meet the team

Quin-C Development

So it is very understandable that everyone seems to think only one person is working on Quin-C. The reason for that is that only one person responds on the message board, only one person writes blogs, and only one person maintains the website. Since that person is me, I figure I would take this opportunity to both explain and dispel this perspective (thought I am flattered by it). The explanation is super simple: I am really passionate about Quin-C and also, more importantly, I am the only native English speaker in the group. This means that when it comes to writing it is pretty much me and only me, which is why it looks like I am the only guy behind the curtain. However, that simply isn’t the case. So to dispel that issue once and for all I thought I would introduce you to key players on the team (the team full development team is just over 20 people and growing).

Read More

tleehealey | Thursday 27 September 2018 - 11:11 pm | | Default | No comments
Used tags: , ,

QView

A new way to view documents in Quin-C

I have written on the topic of viewing documents in the web in my last posting so I am going to skip much of the background related to this topic. If you haven’t read that blog please give it a quick once over. What I want to discuss in this blog post is the new integrated viewer we have introduced into Quin-C. For those of you that did read my previous blog you will know that despite the many techniques that Quin-C uses to enable superior web viewing, in the end those techniques do fall short of the perfect solution. The issues we have not been able to overcome are as follows:

1) The time and space associated with document conversion.

2) The viewing of documents that don’t convert to pdf well such as excel documents and cad documents and things like that.

3) The overall better viewing experience of a desktop viewer.

Read More

tleehealey | Wednesday 05 September 2018 - 7:22 pm | | Default | No comments