Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Blue
Created By: Shannon Scoffield
Created Date/Time: 9/18/2013 4:38 pm
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
 
Time Id: 1762
Template/Type: Daily Ideas
Title/Caption: Daily Ideas
Start Date: 8/30/2013
Main Status: Active

click to enlarge - photo by: Shannon Scoffield -
click to enlarge - photo by: Shannon Scoffield -
click to enlarge - photo by: Shannon Scoffield -
click to enlarge - photo by: Shannon Scoffield -
click to enlarge - photo by: Shannon Scoffield -
 


Notes:
-These are some notes from a phone call with Steve on 8/30/13. We were talking about future vision and how to help fund future projects inside of adilas.
-This is “your adilas”!
-Just in time custom code.
-Login and check out the projects. Then circle back around.
-Focus on community.
-Maybe a custom label management tool. Be able to add custom labels to pages. Maybe use an icon instead of a link. Labels may need to be added on main pages and/or on line items.
-How many pancakes on a plate? Basically, how many corporations or worlds on your server?
-For eCommerce – We need to set the customer type behind the scenes instead of letting a customer choose that setting. This would be great corp-wide setting for eCommerce.
-In training we heard two new words that will end up being used as adilas terminology. They are: Customer facing and frontend programmer. Both phrases came from the graphic associate at the training. Customer facing means which parts and pieces are open to your customers or the general public. A frontend programmer deals with settings, permissions, and interface vs. a backend programmer who deals with code and database stuff.
-We would like to use elements of time to show and track funding on future projects.
-We like to use the analogy of water turning into ice. This is how we track data and operations and accounting. (Water – slush – ice). What if we do the same things with ideas… say something like this… ideas – projects (potential) – development & project funding – tools & functions for adilas.
Basically, we have tons of ideas, it would be cool to turn some of the ideas into projects, get project funding, do the development, and then roll out new tools and features.
-Scientists do the same thing in a way… Scientific Method: ideas – hypotheses – theories – eventually leading to laws (not exactly sure of the order).
-What if we helped our users (virtually community) to help in the idea, project, funding and development process.
-Phase 1 of our development (meaning adilas as a company) – We thought it out, we planned it, we funded it, and finally rolled it out for use.
-Phase 2 of our development (meaning adilas as a company) – We show the ideas and open it up to the world and then ask for help. Have people re-think it (multiple different topics and levels) and be involved.
-Steve also mentioned “fracturing” or “breaking”. Sometimes we look at those as bad or unwanted. Maybe we need to build in order to break of fracture things. That is kind of scary but maybe breaking is or could be good. This topic is definitely scary, but maybe it is needed. Interesting concept!
-Steve put it this way… “Expose the thin ice!” People want to see that. It seems kind of scary but maybe that will help in progression!
-The whole thing comes back to just in time custom code or just in time code. Interesting!
-Build and break, build and break, build and break! That is progress!