Skip to main content

From the Lab: numeroom.com updates.

The beta launch of numeroom.com last week has been instructive in many ways , it has allowed me to finally get over the launch jitters and the many questions of "is it ready" to now be in a proactive mode of "what can I make better?". That said, I have identified several areas that can enhance the experience of new users and I will detail them as they are being identified and engineered for deployment to the production servers. These posts will serve as an inside look into the problems that users have that the site builders rarely anticipate and how they are solved.

Problem 1: Numeroom must be separately created.

When I first launched the site, I had a feeling I should write the registration logic so that it would automatically create a default Numeroom for the Users, this way they could get going immediately with inviting people, sharing files but more importantly , harnessing the suite of following features enabled uniquely by the Numeroom ecosystem in the form of file sharing events, category shift events and jump to events. These allow numeroom users insight into the actions of their contacts that no other collaboration system provides enalbing them to collaborate with a sense of immediacy here to for unknown. Unfortunately, I was focused on hitting the launch and decided to launch with the numeroom creation as a separate action from account creation, big mistake for several reasons.

  • If you are offering something new to people, then talking to them about it won't lead to the "ah ha!" moment. You have to show them, and the less you require they have to actively do to be shown the magic the better.
  • People get frustrated quickly when looking at a new UI , even if it is "logical" to you. Do as much as you can for your users leaving only the pure experience (sharing , chatting, following) left for them to decide over.

So, earlier this afternoon I started plotting the strategy for solving this problem, it can be solved quite literally in minutes, tested on the development machine (the same one I write this blog post on) and deployed to the production cluster in Texas using a numeroom, of course. ;) I'll update the blog when it is done.

Problem 2: Numeroom creator settings not accessible when User is in room.

This was something I meant to do before the launch but didn't get to in time, if a User is chatting in a room , allowing them to find out "who owns this room?" and as well be able to see that owners list of jump to rooms, send that user an IMail or a contact join request is key to quickly enabling them to build a network of contacts with rooms of interest. The faster I allow users to connect the faster the entire ecosystem builds value from those real time relationships. I performed the change which simply amounted to hyperlinking the room's name as displayed in the upper left corner of an active room window. Clicking the link now takes the User to the owners settings page where they can perform the aformentioned actions. Production rollout to follow.

So that is what is in the works for deployment to production, mostly likely tomorrow afternoon.

Comments

Popular posts from this blog

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…

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 …

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…