Skip to main content

Easy feedback added.

Since launching the beta of the www.numeroom.com web site I've contemplated adding a formal forum for feedback from the user community. I have "help" rooms set up for real time interaction but the critical mass of users is not there yet to take advantage. Setting up the forum would not be too much work as the AgilEntity framework has "forum" as a managed entity type, however that would require some integration time (say a day) ... while going over the results of an test twitter ad campaign that I started with the site www.magpie.com ( a post to come on how efficient this seems to be compared to Facebook ads...) I noticed the "feedback" tab they have prominently displayed on the right side of the screen. I clicked on it and was taken to a well designed voting system for "ideas" submitted by users of the site. This was a custom implementation of exactly the feedback that I needed for my site. So rather than spend a day adding it using an AgilEntity forum, I simply created a new account at the site behind the forum www.uservoice.com and added that into the numeroom home page within minutes in development and after a quick test phase within minutes rolled to the production servers in Texas. The usefulness of the distributed infrastructure business models becomes readily apparent when a focused piece of functionality can be added to a site so easily. In fact www.numeroom.com does the same thing but for secure collaboration and file sharing, any business or individual that lacks the expertise , time or money to implement their own solution can simply license it from us. Back to the numeroom.com feedback, I placed some ideas that I already in mind for the site as initial suggestions, if you have a beta account or just have an idea on how the site services can be made better go suggest it or vote up the existing idea.

Comments

Popular posts from this blog

Highly targeted Cpg vaccine immunotherapy for a range of cancer

Significance?


This will surely go down as a seminal advance in cancer therapy. It reads like magic:

So this new approach looks for the specific proteins that are associated with a given tumors resistance to attack by the body's T cells, it then adjusts those T cells to be hyper sensitive to the specific oncogenic proteins targeted. These cells become essentially The Terminator​ T cells in the specific tumor AND have the multiplied effect of traveling along the immune pathway of spreading that the cancer many have metastasized. This is huge squared because it means you can essentially use targeting one tumor to identify and eliminate distal tumors that you many not even realize exist.

This allows the therapy for treating cancer to, for the first time; end the "wack a mole" problem that has frustrated traditional shot gun methods of treatment involving radiation and chemotherapy ...which by their nature unfortunately damage parts of the body that are not cancer laden but …

Engineers versus Programmers

I have found as more non formally trained people enter the coding space, the quality of code that results varies in an interesting way.

The formalities of learning to code in a structured course at University involve often strong focus on "correctness" and efficiency in the form of big O representations for the algorithms created.

Much less focus tends to be placed on what I'll call practical programming, which is the type of code that engineers (note I didn't use "programmers" on purpose) must learn to write.

Programmers are what Universities create, students that can take a defined development environment and within in write an algorithm for computing some sequence or traversing a tree or encoding and decoding a string. Efficiency and invariant rules are guiding development missions. Execution time for creating the solution is often a week or more depending on the professor and their style of teaching code and giving out problems. This type of coding is devo…

AgilEntity Architecture: Action Oriented Workflow

Permissions, fine grained versus management headache
The usual method for determining which users can perform a given function on a given object in a managed system, employs providing those Users with specific access rights via the use of permissions. Often these permissions are also able to be granted to collections called Groups, to which Users are added. The combination of Permissions and Groups provides the ability to provide as atomic a dissemination of rights across the User space as possible. However, this granularity comes at the price of reduced efficiency for managing the created permissions and more importantly the Groups that collect Users designated to perform sets of actions. Essentially the Groups serve as access control lists in many systems, which for the variable and often changing environment of business applications means a need to constantly update the ACL’s (groups) in order to add or remove individuals based on their ability to perform certain actions. Also, the…