all data is live and searchable
[reset this page] .
[historical web outline - entries by month] .
[adilas community funded projects] .
[contact adilas.biz support - email form] .
[help]
|
Adilas.biz Developer's Notebook Report - 9/1/2013 to 9/30/2013 - (47)
|
||||||
|
Photos
|
Time Id | Color | Title/Caption | Start Date | Notes | |
|
AU 1764 |
|
Daily Tasks | 9/2/2013 |
• Updated a commercial video for a client’s website. Posted new files online. • Reviewing notes and notebook files. Read my sister’s notes from training. • Sent an email to a graphic associate about a new graphic assignment to help create and meet the player groups for adilas. This deals with the 12 main players and how they interact, play and function. This is kind of like introducing groups of people for a movie or book. We are hoping to make it fun and fresh. • Posted a new YouTube video online. • Recording notes from the past couple of days. Brainstorming on ideas for showing people our to-do list. • Went in to Smithfield to work with my dad, and two brothers. My dad and I played with his “direct to edit” video recorder. This takes a standard video camera and skips the old analog tape and goes right to digital storage. This saves time on rendering and digitizing files. We are really excited about this. I met with my brother and got him some money. I met with my other brother and he showed me some ideas he has for some adilas commercials. I’m excited to see what he comes up with. Good things are happening! 20 miles. • Working on a new training flyer for September. • Posted the new training flyers online. Updated the news and update page. |
|
|
AU 1767 |
|
Daily Ideas | 9/2/2013 | -I was on a drive around the country side and saw lots of farms… I kept thinking about the old saying, “The work is never done on a farm.” Meaning it just keeps going and going. There is always something that needs to be done. | |
|
AU 1765 |
|
Daily Tasks | 9/3/2013 |
• Recording notes in my notebook. • Emails and tech support. • Working on a payroll change for one of our team members. She needed some people switched between departments. • Working on a new page to empower the users. • New logo for a company. • Working on the change department page for users. Tested and posted new files online. Sent an email update to our team member who had requested this feature. • Adding expense/receipts for adilas. Making a credit card payment. • Talking to a contact about helping with some adilas work. I’m going to have here start helping to document the internal adilas API (application programming interface). I told her that I would have a small project ready by Thursday. • Meeting with my brother’s girlfriend about doing some adilas work. I’m going to start her on some data entry stuff and maybe lead into some graphic stuff. She is going to be helping with loose brainstorming pages and papers. This will be part of the developer’s notebook. Good meeting. |
|
|
|
AU 1768 |
|
Daily Ideas | 9/3/2013 |
-“Data in detail” – Quote by my father on 9/3/13 while on a morning walk. He said that one of the things that make adilas unique is – “Data in detail.” Another one from him is, “Not all data is created equal.” – February 2013 training session. -The receive invoice page needs some pagination. It also needs a paid date to be shown. This is an older page that has not had much action for quite some time. -We talked about doing a “get to know you” flyer for the groups and system player groups. I also think we need to do similar type flyers for the functions and core concepts. We need to let people know what we are doing! -A future project might be to document what each page inside of adilas does and what page params it allows and/or requires. -On the adilas API (application programming interface), we need to check for an SSL connection. If not, we need to prompt. If any decoding is needed, we need to decode or encode values as needed. This needs to be done on the application level. Not at the user level. -When showing the tech level of the API or adilas university – Go by function not by page. Show the concepts or how the different methods work and function, not necessarily how our pages work and flow. Show the users what is available to them through the API. If needed, show main page flow. This should help the end user understand what is going on. |
|
|
|
AU 1766 |
|
Daily Tasks | 9/4/2013 |
• Phone calls, emails and tech support. • Reviewing to do list and starting on a customer upload for a client. • On the phone with my sister. We are trying to figure out what our current projects are and what direction to jump. Good phone call. She is going to help push the developer’s notebook project ahead. I’m hoping that my brother’s girlfriend is able to help her on that project. • Back on the customer upload for a client. |
|
|
|
AU 1769 |
|
Daily Ideas | 9/4/2013 |
-On a walk this morning with my dad – We heard some dogs barking but we couldn’t tell where they were coming from. We decided to check it out because something wasn’t right. There were two dogs and they were stuck on a cliff band. Who knows how they got there. We scrambled up and checked it out. The dogs were fine but we didn’t know where the owner was. We looked around, yelled, whistled, etc. Anyway, we helped the dogs get out, called the police, and waited for a call back. It ended up that the dogs had been lost for three days and the owner and the dogs got re-united. We were grateful that the owner wasn’t missing. It is crazy to see how fast our own little world can be flipped into a different scenario. Life is very precious! -We have had requests to turn the customer tax category into a real setting. Currently, it is only a reminder and shows a warning if not used correctly. People are in such a hurry, the little warnings don’t do the job. They just glance right over them. People want things automated and easy! |
|
|
AU 1770 |
|
Daily Tasks | 9/5/2013 |
• Went into town to meet with the folks about tracking the Bear 100 runners and using adilas to do it. I watched and listened to what they had going on and how they were trying to fix it. They have fixed one of the pieces but also introduced tons of new requirements and variables into the puzzle. My presentation was a simple drawing and then a couple minute presentations of what adilas could do. I was having fun. My dad and two other guys were there. Good meeting. 30 miles. • Emails, phone calls, and tech support. • Working on a new set of pages to help document the current adilas pages. This is the start of the adilas API (Application Programming Interface). Planning out and adding new database tables to hold the documentation pages and information. Added eight new tables. One for the main page of function, one for modified log notes, page comments, page parameters, page results, page sub results, page samples (code), and a history table to record the changes made. |
|
|
AU 1791 |
|
Daily Ideas | 9/5/2013 |
-Tools don’t promise a finished product. Tools promise a job or task if used correctly. -The more I think about it, the more the model favors a Just In Time (J.I.T.) mindset. JIT code, JIT calculations, JIT interfaces, JIT help, JIT data, etc. Just in time is a great model. As a note, Just In Time, still requires some prep but it speeds things up when used properly. -When doing consulting… Make sure to listen and let the customer talk. It they talk, they will help you know where there pain is. It might sound random, but the “pain” is a key part of the puzzle. -Link the help files to the page documentation stuff. This could be done on the API documentation when recording help file values and numbers. Basically, the help files are another part of the page documentation. -Add the permission id #’s to the pages that have the permissions on them. This will be required for future API developments. -Add a whole new permission for add/edit API documentation. -Add a history table to help monitor who updates and changes the API documentation stuff. |
|
|
AU 1771 |
|
Daily Tasks | 9/6/2013 |
• Brainstorming on breaking things and doing maintenance. Mad a bunch of phone calls and responded to a bunch of emails. • Created a new graphic with a gardener making a decision about planting new flower beds or circling back and doing some maintenance on existing flower beds. I also added a fairly long update on the news and updates page talking about maintenance and future vision of what we are doing and where things are going. • Emails and tech support. • New logo for an adilas rep out of South Carolina. Posted new logos and colors online. • Working on the interface to help document adilas code pages and the main adilas API (application programming interface). • On the phone with Steve going over updates and new changes. We talked about letting other companies virtually piggy-back and connect to our API. This could be other vendors, eCommerce solutions, marketing, sales and promotions, gift cards, stats, reports, or interfaces of all sorts and kinds. We also talked quite a bit about recording our own history on the news and updates page. See notes later on. • Working on new pages to record web and API documentation. • Went in to Smithfield to get new video clips from my brother. He gave me five new clips. We talked about finishing this first round of tapes and then starting on new stuff. It is exciting to see the progress. 20 miles. |
|
|
AU 1792 |
|
Daily Ideas | 9/6/2013 |
-Not all progress comes from check lists. -Maintenance – what a huge key. -Load sharing and load balancing. This is for people as well as for high tech computers and servers. Many hands make light work. -We need to tie-in the web page documentation to the main adilas site. This is part of the “tech” level of what is going on. -Here is your challenge… work yourself out of a job. -“Again” – what a great word. -“Let’s see if we can break it!” – The more effort you have put into something, the less likely you want to break it, but many time, if you break it and make it better then you make it stronger. Human nature doesn’t like to make more work. The process of building and breaking, building and breaking takes tons of work. Sometimes you just have to do it because it needs to be done! -A friend of mine – “Give seeds away.” Share the potential with others. A seed has huge potential but needs to be planted and cared for. -I was talking with my friend on the phone. We were talking about different projects and how much time and energy things take. He put it this way, “What are you willing to do for money? Is it worth it?” Sometimes we need to look around and see what our priorities are and then readjust from there. Notes from a phone call with Steve: - We would like and could have tons of outside interfaces. This could be eCommerce solutions and tons of other things that come to us or piggy-back on what we have to offer. We wouldn’t care at all if we had 20 different eCommerce packages that could be bolted on to the main adilas option as part of the API or independent services. Bring it on! - Link all of the pieces together. We have tons of data and tons of options. Help the people link everything together. - On the news and update page… We would like to show the fully history of what was on that page. Including links and photos. This comes back to education and training. - Maybe put something like… We are flying pretty fast – click here to review if you’ve missed something. -Document and archive the adilas database tables and fields. This will also be part of the API. This is another level or layer of the “tech” level of adilas. -Also with the database documentation, it would be cool to show a visual map and how different pieces play together. Help in the learning processes. Lots of time database level information is reserved for backend techs. If we could make it fun and teach the general public, it would increase their knowledge and understanding. This increase ns knowledge will eventually help in future creativity and ideas. -On the API documentation… We need to handle all encoding and decoding on our end. We don’t want other people playing with that piece of the puzzle. That may take a little bit more work but will help with security. -After reviewing a training video, that my brother did, from the first adilas training class, I was thinking about cause and effect relationships. The more you think about it, the more your accounting is a virtual cause and effect relationship or a byproduct of your day-to-day operations. Why would you even need accounting unless you do something? In real life sometimes you have to account for things that you didn’t do as well as things you did. In a way, it is how you spent your time and does that have an effect on something else? Accounting is the natural cause and effect or consequences of being in business or even existing (if you go way out). |
|
|
AU 1772 |
|
Daily Tasks | 9/7/2013 |
• Working with the web API documentation homepage. Adding new pages. Also uploaded new YouTube video clips. • Posted links on adilasuniversity.biz for the 5 new YouTube video clips from my brother. |
|
|
AU 1793 |
|
Daily Ideas | 9/7/2013 | -I was talking to my wife on the way down to a baptism for my niece. I was telling here how I couldn’t control my time. I expressed that it was frustrating not being able to tell clients when certain projects would be done. She made the comment, maybe think about “managing time” vs. trying to “control time”. I liked it, I can manage and that empowered me vs. feeling out of control because I don’t have full control. Interesting concept. | |
|
AU 1773 |
|
Daily Tasks | 9/9/2013 |
• Working on a customer upload. • Emails and light tech support. • Working on the web API documentation section. • Working on the add/edit main page/function code for the API section. |
|
|
AU 1794 |
|
Daily Ideas | 9/9/2013 |
-I had a great talk with a contact. He kept saying, “Build on what you have!” I really needed that. Sometimes I focus on what still needs to be done, when in reality we have a great base. -Keep it simple and keep stacking basic building blocks together. Build on what you have. |
|
|
AU 1774 |
|
Daily Tasks | 9/10/2013 |
• Prep for a meeting with the bank. Printing off papers and such. • Working on the add/edit pages for the web API documentation part of the site. Brainstorming on in-line custom code options. Lots of work on cleaning up random copy and paste values for the API documentation. Writing code to strip out enter signs, new lines, tabs, and multi white spaces. • On the phone with a contact talking about the customer API and doing emails and text message blasts for adilas customer. He seemed pretty sharp and it got me thinking about outsourcing small projects. • Back on the API documentation pages. • On the phone with my sister catching up and getting ready for future projects and such. • More work in the API documentation pages. |
|
|
AU 1795 |
|
Daily Ideas | 9/10/2013 |
-Daydreaming about in-line custom code… What if every link and/or report had settings assigned to it? Say for example, the advanced time search results page. What if I wanted it to be formatted with only certain columns (fields) and in a certain order? How would I record that as a default behavior or result? I think it would be interesting to add code to searches, links, and buttons. Maybe we could define a button, name it, tell it where to show up, and then tell it what report settings to use. That would be very powerful. -What if you could create any of these buttons (above) and then have them show up wherever you wanted? As a group or even randomly around the site? It would also be cool to organize your own buttons and virtually create your own menu type system. Imaging my cart favorite buttons with even more placement options, plus the ability to hold settings, and be able to stack and name the buttons as needed. -It would be kind of cool if you could contain all of the custom buttons in their own environment such as virtual space or icons on a smart phone, iPad, or a standard desktop screen. It would also be cool to be able to place any button anywhere on any specific page. Let the users create their own interface and flow. -What if each page had its own layout grid? This could be awesome but might be too much freedom. Basically where do you want what? And how should it be displayed? This might be a tricky balance between total freedom and total lock-down (rigid). Time will tell… |
|
|
AU 1775 |
|
Daily Tasks | 9/11/2013 |
• Went in to town to meet with some ladies at BATC. We setup in one of their offices for an adilas demo and an interview. They videotaped the interview. I also used GoToMeeting and captured a full screen capture of the session. The interview had a strong flavor of how BATC (Bridgerland Applied Technology College) has played a part of our success over the years. It was a fun demo and got to use the adilas toys. I used the receipt printers, barcode scanners, flatbed scanner, label printer, and the credit card swiper. It was fun and hopefully showed some good vision for the future. After the demo, I stayed and talked some business ideas with one of the ladies. She has a number of health coaches that need a mix between eCommerce, inventory tracking, and CRM functionality. She had some great ideas about eCommerce and potential flow. 30 miles. • My brother came over and we talked about future projects and marketing ideas. He showed me some of his drawings and concepts for adilas commercials. His skills are improving. He also got a new computer that should work awesome for him. We then spent almost an hour using a screen capture product called Camtasia Studio 8 by TechSmith. The product was quite slick and I could see some great potential. We did a few screen captures and recordings on sales, invoices, customer logs, timecards, payroll, shopping cart, my cart favorite buttons, etc. I can see us using this software for adilasuniversity, commercials, and other tech oriented videos. Great meeting! • Recording notes and transferring loose pages into my notebook. My sister had my notebook for a couple of days. |
|
|
AU 1796 |
|
Daily Ideas | 9/11/2013 |
-It won’t be long and we will be able to say – “Adilas is an eCommerce ready point of sale system.” It does a lot more than that but those might be good words to use together. I liked the eCommerce ready part of that saying. -I’m seeing more and more need to build out the eCommerce pieces. That is what people want and think that they need. -Steve and I used to joke… “You can do that???” Or, “You can do that!!!” -We are good at creating and using dynamic templates or dynamic engines. We build once (the engine or template) and then use it over and over again with different or dynamic content. Build once, use many! We used these same concepts on a number of fun projects like the BATC Interactive app., Learn to Freeride (LTF) app., and adilas. It is a great model and very flexible. Build the engine and then allow it to play on multi levels. -What if the actual API calls could have custom stuff added to them? This could be on both passing data in and getting data out. Our current thinking is to expose the API “as is now.” But I can see in the future where some custom options could be beneficial. -This is a side note… but often we have to dream things up in a static mindset. Once we make sure that works; we tend to want more dynamic and custom options. It is a built-in progression of sorts. If you jump straight to dynamic, you tend to get lost sometimes…. Too many options and you no longer can tell what is the most important. I’ve see this many times. -My brother had the idea about creating custom adilas interface options. He would then sell them for $10 a piece over eCommerce. This would be like clothes or different skins. I’m not sure where this would go but I wanted to record the idea. I can see him doing this and then contacting us and having us put the custom interface in place. It would be cool if it was already wired up, had its own help file, documentation, and then it could be added either manually or automatically to the users options under their chooser. Maybe this would require the artist to submit the interfaces for review and wiring. Then we could hold them and let people purchase the interfaces as needed. Anyway, just some options. -Another idea is to have the artist create the custom interface, pay for it to be wired up, and then be able to sell it. Basically, the artist pays for the storage and wire job and is then able to sell it as an add-on to the basic adilas package. We, adilas, would then have to track that and give a kickback to the artist. -Another idea from my brother, we could play a small intro video for a subject during a training to get the ideas flowing. Then we could talk about it and see where the questions are after watching the intro video. Great idea! My brother, said that he loves to see what is possible and then he is more willing to learn it if he wants that as an outcome. I thought that is was a great comment. |
|
|
AU 1776 |
|
Daily Tasks | 9/12/2013 |
• Recording hours and transferring notes from loose pages to notebook pages. • Finished up transferring notes and recording ideas. I love taking notes… it helps me remember things. If not, everything tends to blend together into a mush of random pieces. • On telephone with a college student. He wants to help with some adilas graphics and such. He will be coming over later today for an interview. • Did some prep on the World Building flyer for adilas. I’m going to put him on that if he thinks it is a cool idea. The fun part about the prep was photo copying pages out of my notebook for him. I’m excited to get these files up and online. • This student came over to my house and we had a little meeting. My sister and I met his up at the University on 8/30/13 while waiting to talk to a professor. Anyway, he got to my house and I got to see some of his art work. It looked great and had a fun geometric balance to it. Once we were finished with his stuff, we started to talk about World Building and what we are hoping to do with that. Lots of concepts. I gave him a small stack of papers with ideas from past notebook entries. It had sample graphics, notes, and ideas I gave him the assignment to start watching YouTube videos and getting familiar with what we are doing. We will be meeting next Tuesday. • My sister came over and we did a training session on expense/receipts and balance sheet items. We did flex grid stuff, we did payments on account, we did ACH stuff, etc. We scanned receipts, invoice, credit card stuff, etc. It was a great exercise. We even got in to problem solving, did bank reconciliation, and found a duplicate check. All real and all live training. She did awesome and was flying around the site. Great meeting. |
|
|
AU 1797 |
|
Daily Ideas | 9/12/2013 |
-“adilas engine” or “adilas core” – Thinking about bolt-on products to the adilas engine or the adilas core. I think either one may work. I kind of like the adilas engine visual best. -I was thinking about getting help on different projects. What if we fully documented specs for the project, included all requirements, brainstorming ideas, wanted flow, and even possible mock-up screen shots. Then posted the projects online and let outside developers bid or see if they are interested in the project and/or the job. Basically, let interested people find us instead of us staffing and finding all the talent and skills. There are pros and cons to this but I wanted to record the option. -One thing that my dad said was… Interns don’t have to come from the University or College. Basically, keep an open mind and look for and find talent wherever you can. -Note on this student’s idea about getting rid of Accountants. He had a thought… what if we could get rid of the job Accountants? We could layout the categories and then plug stuff into the slots on the correct days. Make it real-time and just plug things into a linear spreadsheet of sorts. Anyway, after he got done telling me his idea, I told him that he would love what we do. Instead of using a simple spreadsheet and plugging in the values, we use objects and data and run it over time. His idea is very similar to the financial history report that has not yet been build. Here is a rough sketch of his idea…. … Date 1 Date 2 Date 3 Date 4 Date 5 Date 6 ….. Totals Category 1 100 100 … … … … … 200 Category 2 … 10 … … … … … 10 Category 3 300 … 500 200 … … … 1000 Category 4 … … … 250 … … … 250 Category 5 200 … … … … … … 200 Category 6 … 700 … … … … … 700 ….. … … … … … … … … Totals 600 810 500 450 0 0 … … Imagine time across the top in days. Down the side would be the different financial categories. The numbers would then be plugged in where they needed to be or what happened. So… to take that to the adilas level… Imagine something very similar but the values would be fed in from underlying data and objects that are carrying that data. Each data point would be a drill-down link to the underlying data. The actual dates at the top would be a drill-down to the effectual history report for that day (what shows up for roll call). The categories could be links to details filtered by the categories. Basically, instead of plugging the data into specific spots, the system would map and roll call the data to the spots. The spots (data points) would then become the drill-down links to the underlying details. If more detail is needed, you could have different views of the report and expand sections as needed. If you want even more details, you could click on the objects themselves. This could allow for the full one-to-many relationship, any photos or outside documentation, system histories, and links to other pieces of the puzzle. The whole story right at your fingertips! In a nutshell, this student’s ideas prompted me to write out more of what we were thinking about clear back in January and February of 2011. If you want more info, go the adilasuniversity site and search elements of time for the word “financial”. You’ll get some good results. |
|
|
AU 1777 |
|
Daily Tasks | 9/13/2013 |
• Brainstorming on ideas for referral marketing. Wrote an email with the ideas. It was dealing with a per head count for getting people to training. Sent the email to a number of different people to see what they thought. I then recorded some notes from yesterday. As part of that I expanded on a student’s idea of linear real-time financial overlook type report (not sure what to call it). See the notes for yesterday. I also wrote an email to Steve and David explaining the concepts of the adilas engine and how we could use the engine as the core and then skin or put a custom interface on top of that. • Recording more notes on referral marketing ideas. • Went in to Smithfield to work with my brother on video stuff. He gave me the last five videos from our first February 2013 adilas training session. That is exciting! He spent hundreds of hours on that and produced 54 video clips and hours and hours of edited video. He is already starting on the August training course that we did just a couple of weeks ago. Good stuff. 20 miles. |
|
|
AU 1798 |
|
Daily Ideas | 9/13/2013 |
-Referral marketing idea… $10.00 a head per day for active participation in the free adilas training course. This goes to the person who got somebody to go to training. Cap it at $100 per day or 10 people per person who did the inviting. The person who attends the training doesn’t get paid; they just get the free training and get inspired. The benefit to adilas is in the referral marketing and realizing how for that training can go. People love our product once they know how to use it. If they don’t take the time to learn it is like expecting a saw and a drill to build your porch. If you know how to use the tools, you (meaning the person not the tools) can then build a porch. Tools require skilled operators! Why not incentives or encourage people to get trained. I wrote a whole email with this idea in a proposal type format. See the email from 9/13/13 with the subject of “A referral marketing idea.” -Along with this same referral marketing idea… We could do different amounts for smaller blocks. Say $5 a head for smaller 2 or 3 hour demo sessions. This $5 a head helps pay the rep for opening his/her mouth. Then hopefully they, the reps, could pick up new accounts and/or get one-on-one demos setup. It is a small little amount up front with the possibilities of landing actual real deals. -Maybe we could try small info sessions and do ice cream or pizza or pay the per head amount. Basically, most people don’t want to give up their time and effort for nothing. -We may also get certain people and pay them to man booths, tables, or do flyers. Ideally, these would be reps that know the product and could get some business out of the events. -As a note, if we did do the referral marketing ideas… We may need some way to verify things to make sure people don’t say they have a certain number of people and they really don’t. Just as ideas… a video of the session, a photo, a recording, paper reviews, contact info, or a digital sign-in sheet. The digital sign-in sheet could help the rep get back in touch with the people who come to the events, training, demos, or work sessions. Heck, they could eve use adilas, create an element of time and assign customers (prospects) to the element of time. Once we add a photo gallery for time, they could document the event. Tons of options. -Another idea is to co-sponsor an event with an adilas rep or consultant. Then the visiting adilas team member could vouch for what goes on and numbers for the event. -Tons and tons of mini events, training sessions, and demos. Small blasts may work better than multi=day training events. -An idea from my brother – show the potential of each group within adilas. There are 12 main player groups. Set up a teaser video that shows what is possible and what flavors each group had and/or is capable of. Almost to the commercial level per group. For example: Invoices are one of the 12 groups. -Invoices could have customer, multi-customer, no customer; tied internally to a stock/unit, be a transfer invoice, be a transition invoice, be an eCommerce invoice, have one line item, multi lines, hidden lines, mixed tickets, elements of time, on account, single payments, multi payments, change due, disclaimers, custom verbage, special paperwork, photos and scans, signature lines, different views and sizes, etc., etc. Show the group overview in a commercial type video setting. -We are going to need a centralized place for our visual teaching tools, graphics, analogies, video clips, and other animations and assets. This could be on adilas university or under the button on the interactive map that reads “objects & data over time”. That button is right smack dab in the middle of the map. -On eCommerce, we need a setting that will allow shipping to be skipped. For example: a downloadable product or a service or a booking or reservation or a rental. Adilas does reoccurring payments and monthly subscriptions, that doesn’t need any shipping info. We might need the option to be smart… meaning can the system tell if the items be purchased are physical or unlimited. -We need the option of sending an email with custom verbage and/or custom information. This could be general day-to-day use or notices or it could be part of eCommerce. As a note, this email and/or text message capability may need to be a setting or a one-to-many between corporations and items or corporations and transaction types. It may also need to be dynamic or user driven. -We need to ask a few different corporations for permission to show other potential clients or people how they use adilas. This would be strictly for demo purposes. Another idea is to literally make a small commercial of how they use adilas. We could film them using it, them showing it, and then let them see the final video. Then we wouldn’t even access to their site. -Dealing with tools that we expect to do the job without any manual intervention…. I was thinking about the Disney/Pixar movie “Wall-E”. At one point the captain is presented a user manual (a book). The captain gives a verbal command of “Manual Open!” Instead of saying manual like a user manual he says it like a Hispanic name of Manuel. Eventually the robot Auto (huge play on words) physically opens the book for the captain. This whole scene is a light play on words between manual and auto. Long story short – we almost expect tools to be at an auto level. However, many tools are made for manual usage and do nothing of themselves. Think of a power saw and a power drill – they will just sit there until picked up and used. In the right hands, those two tools can help to make beautiful work and do a great job. |
|
|
AU 1778 |
|
Daily Tasks | 9/14/2013 |
• Recording notes in notebook. • Emails. • Uploading videos to YouTube. |
|
|
AU 1779 |
|
Daily Tasks | 9/16/2013 |
• On the phone with Steve. We talked about tons of custom projects and where we need to focus. Steve is on a number of custom projects and I have a number of projects. We talked quite a bit about custom documents, API code, and server stuff. We also talked about training stuff and getting two other associates into key positions inside of adilas. • Emails and follow-ups. • Posted two internship/job listings on Career Aggie for USU. • Writing emails to professors up at USU letting them know that we are looking for interns. • Working on pages to help finish up the school tracking pages and section for a teacher. Added a new assignment filter to elements of time. The new filter allows for a list of id numbers instead of just a single user id. Tightened up the flex grid search for users who have the limited customer search permission turned on. I also added a new button on the view standalone flex grid page to help filter the flex grid tie-in records per main id number. This allows for options to export to Excel from a single record without knowing the main id. In a way, it is a way to filter the existing standalone flex grid records just by passing some known values to the existing flex-grid tie-in search. That should really help. |
|
|
AU 1799 |
|
Daily Ideas | 9/16/2013 | -Teach tools and concepts. Apply what you learn. Mix and blend to get the results you want or need. | |
|
AU 1780 |
|
Daily Tasks | 9/17/2013 |
• Working on help files and going back through projects that are hanging out there. • On the phone with a rep going over my cart favorite buttons and future needs for clients. We talked about elements of time and how those are going to be playing more and more as we go on. • The college student I met with previously came over and I gave him a quick demo of adilas. We popped into a couple small interfaces, added an element of time, and changed some permissions. He has quite a sales mind and it is fun to watch him think. He is actually more of a salesman than I thought. His idea for the day was quick 30 second clips on the permissions and what they do. I could use those all over the site. • Emails and recording notes. • Emails and tech support. • Help files and prep for next training course. • On the phone with my brother. He had some video and commercial ideas. He thought that it would be fun to show barcode scanners, label printers, check printing, and credit card swipers with real video. We also talked about overview commercial and showing what is possible. The other thing we talked about showing some of the adilas history like the silent section of the Disney/Pixar movie “Up”. Show a progression over time. That little piece of history could really help people understand where we came from and where we are headed. |
|
|
AU 1800 |
|
Daily Ideas | 9/17/2013 |
-Spread out tons of tiny video clips inside of adilas. Have some sort of little icon or link or image where people can get help on anything inside of adilas. Basically, take adilas university and have it all over the place in mini segments around the site. It will all be together on the adilasuniversity site, but spread around inside the main site. -Adilas is like an iPhone or iPad. It has tons of potential depending on what apps you install and use. Inside of adilas it depends on permissions, settings, tools, and features. |
|
|
AU 1781 |
|
Daily Tasks | 9/18/2013 |
• Went in to town to visit with the some folks. I gave them a small adilas demo and we talked about what options we bring to the table. They do custom jobs and injection molding. We talked quite a bit about relationships and tying things together. I told them that I would get them a quote for our service. 20 miles. • Emails and technical support stuff. • Prepping a quote for this company. Printed off different documents and such. • Working on an add core data in bulk page for the teacher/ student interface. • Working on the add core data in bulk page and flow. |
|
|
AU 1801 |
|
Daily Ideas | 9/18/2013 |
-“Build on what you have!” – I love that saying! -I’m seeing more and more need the content server. People need to create an object and then be able to attach whatever items, paperwork, custom files, etc. to that object. The need is huge. -Job costing is another big need… We could use transitional invoice, stock/units, or elements of time. We have also seen people use locations to track job costing. I’d love to figure out a simple way to do job costing that is easy and logical. We’ve got to be able to come up with something. -For some of these data intense flows or tasks… it would be awesome to create a simple flow chart to help the users. -I can also see the need for custom mapping and settings for figuring out accounting and flow. What are the dates, stamps, and status of the different checkpoints? -What it, for me, I charged $1,500 for 5 – 2 hour sessions. Basically, I could get a company up and running for $1,500 with no problem. This assumes that after that it would go in to an hourly rate of $100 per hour. I’ve got to make it worth my while. |
|
|
AU 1782 |
|
Daily Tasks | 9/19/2013 |
• Emails and tech support. Got a call from a client about the new Texas 130-U application form. • Adding an option for Steve to be able to upload to the public folder on adilas. • Prep for interviews. Emails and getting things lined up and ready. • Went in to town to conduct some interviews for adilas interns. I picked up my sister and we went in together. On the way we were talking about tools and what they do and what they require. We then started talking about models and how to break models and tools. That was fun. We even talked about how to break our (adilas) current model. We talked about where it needs to go and how to get there. We got to the University and met our first appointment. She was from India, what a sharp cookie! Both my sister and I were blown away and she seemed to be just beaming with potential. She had done some research, she had good questions for us, she presented herself very well, and both my sister and I were smiling the whole time that we talked. Great interview. For our next interview it was another lady and she had smaller skills and lacked confidence. My sister and I then had a brainstorming session waiting for our next appointment. We were talking about how to introduce our system players and groups. We talked about introductions, abilities, What does it do?, Who are its friends?, How does it interact?, What are its weaknesses?, Limitations?, and Shortcomings? We talked about usage and frequency. As we got deeper and deeper into the analogy my sister had the idea of going clear up to the “world” level. We talked about an analogy of going to an ice cream shop and virtually choosing your flavor. Very diverse and no good or bad choices – just different flavors. We also talked about basic intros and then branching according to flavors. Great brainstorming session. We then drove to Bridgerland and met with a lady. She was at the last adilas training session. All three of us continued the brainstorming that my sister and I were doing up on campus. We ended up with ideas that the business functions that adilas does or ways to use the system are like our menu options – what do you want? The groups of application types (players) are the pieces we mix and blend to get you the results you are looking for. As we mix and blend system players we can give the desired business function or outcome. We had a good time. As far as the core concepts and theory, those pieces are the supporting roles or foundation that create the malt shop itself. They are ever present and support the functions and players. After our meeting we setup this associate with her own little adilas account. 30 miles. • On the phone with my brother trying to figure out options for video editing. I got an email from Steve and David about cost and what we are getting for that cost. Good stuff. We may need to alter our current flow, but good stuff. |
|
|
AU 1802 |
|
Daily Ideas | 9/19/2013 | -Doing nothing will break every model and every tool! | |
|
AU 2293 |
|
Brainstorming - How to Introduce the Main Players | 9/19/2013 |
Small Brainstorming session on how to introduce Main Players: Example: Introducing main players like introducing groups – [like LOTR (Lord of the Rings) hobbits, elves, etc.] Personality…. Start with tools – move to – World building – move to – flavors (your flavor drives, guides the world you build) – Main Piece Possibilities vs. Limitations of the Players: - What are you?/ Brief Intro: - Abilities/What does it do?: - Friends /How does it interact?: - Weaknesses/Limitations/Shortcomings: - How much are you used?/When are you used? Interactive commercial: - General info intro: - What’s your flavor? - Multi-media - If you let people select at the different levels – show them where to change that or how to make it happen. (corp-wide settings – screen shots, etc.) - Commercial on Application Players: o Customer o Vendors o Etc., etc., etc. Approach it from the world view – Basic General World - Do we need to make it applicable for different flavors? Such as: standard retail, big tickets, services…..clinic, etc. Other notes and an example with customers: - Customer Homepage o Search o Advanced search o Log o Add/edit - Contacts o Add/edit o Search - Notes & logs & follow-up o Add/edit o Search - Photo - Flex grid |
|
|
AU 1783 |
|
Daily Tasks | 9/20/2013 |
• Writing an email to Steve and David about the progress we are making. Money is tight but progress is being made. It is a tight balance sometimes. • Recording hours and notes from yesterday. We had a great day with lots of new developments. Things are going pretty fast right now. • Working on the teacher/student interface. Responded to some emails and went back and reviewed some great notes from 12/24/12 dealing with customers and competition. My brother came over and we talked about a video editing game plan. We also lightly talked about sales and drumming up some work. |
|
|
AU 1784 |
|
Daily Tasks | 9/23/2013 |
• Responding to emails. Sent a couple to Steve and had a bunch of other ones for interns and college students. • Answering tons of other emails. More resumes and intern stuff. Sent a number of different emails to different reps. Light research. • On the phone with Steve going over his custom code stuff. He had some questions about using methods and components inside of ColdFusion. His skills are increasing and he is helping me to spend my time on other projects. We also talked about marketing plans and where we are headed. We also talked about credit cards and funding future projects. We have to be careful how we use our funds and which projects get priority. • Met with a guy up on campus to do an interview for the adilas assistant web developer position. Sharp guy and had some good computer and web skills. • Working on the add bulk flex grid tie-in page for the teacher. • Met with another guy who was interviewing for the assistant web developer job. He was very sharp and did a great gob. He passed all of my little tests with flying colors and was fun to talk to. Great interview. I offered to pay him to come to training. We also talked about other future options and potential. He seemed very solid. • Working on the add multi flex grid action page for the teacher/student interface. |
|
|
AU 1785 |
|
Daily Tasks | 9/24/2013 |
• Finished up the add multi core data (flex grid tie-ins) page for the teacher and the teacher/student interface. Posted files online. This is the first page that adds multiple pieces of flex grid in bulk. Pretty cool! • Went in to Logan for day one of the adilas training. I have been kind of sick and dealing with allergies. My sister was able to step in and help out multiple times through the three-day course. These notes were recorded after the fact on 9/28/13. Anyway, once training started only my sister and I were on the GoToMeeting seminar. We started to work on a brainstorming document dealing with tools, what they do, how we use them, what are the features, advantages, and benefits? We also talked about limitations and how to break different models. Eventually we had some others join us and we even un-muted a contact for a discussion on web and cloud stuff. We spent the first hour talking about the different tools. We did have to shut down and restart due to some technical sound issues. One of the guys that I interviewed up on campus came to the class in Logan. He is a USU student and came for an interview/training. I actually interviewed him on 9/23. As part of our training course, I had both my sister and this guy take turns teaching and showing different concepts. That helped me with my voice and also gave them chances to teach and have some hands on learning. Good stuff. After lunch we were joined by others and another USU student came to see us. It was really fun to see the younger generation take to the system. With minimal effort, they were able to navigate around and get the tasks done. The topic for the day was sales, inventory tracking, and other point of sale features. We touched on invoices, customers, vendors, parts, services, PO’s, recipe/builds, barcodes, labels, and credit card scanners. We touched on flex grid and even got a lesson from one of the interviewing interns on how data was stored in databases. I though the class was very good. 30 miles. • Emails and light tech support. Contacting USU interns and potential candidates for the assistant web developer position. |
|
|
|
AU 2146 |
|
Adilas 3 Day Training Notes - Logan | 9/24/2013 |
LOGAN SEPTEMBER 2013 TRAINING Day 1 - -Tools brainstorming: Most tools have a great capacity but they have to be used to actually be able to function. Input necessary... one way to break any tool ever found... doing nothing. -Tools that we use: Features, advantages, and benefits... vs. Limitations and how do these tools break? -All data is live and searchable... serviceable... scalable... sustainable and secure. -Databases - relationship, relational models - stored in tables, references, potentially able to store millions and millions of records to connect, reference, relate with main ids, sub identifiers, with cascading effect. (Never tie things by name in a database table but by id tags/reference because then you can change the names (customize it) and still make all of the database connections) -Once something is in there you can search it - - you just need to know what field or area you are searching ***IDEA: What if you even listed out what people could potentially want to see after they have a function... or what options they have... it's in the links but maybe even knowing what thinks are available would help to know flow or where it shows up... -Sanitizing inputs - tech talk |
|
|
AU 2294 |
|
Brainstorming Tools - Their Features, Advantages & Limitations | 9/24/2013 |
This Document came from the September adilas training course, 9/24-9/26/2013: Tools that we use: Features, advantages, and benefits: Limitations and how do these tools break: 1. Head and mind a. Always on, not limited, imagination, switch at will, creative, huge capacity. b. Think through things, process clear to the end without actually committing, different scenarios, multi-tasking even while doing other things. c. Unlimited capacity to learn and process. d. Start here and translate to other processes. e. Limitations – Recall, searching, memory, what you do know, knowledge, affected by outside sources. f. Break the mind – sleep, eat, and intake. Volume and number of transactions. g. Complexity 2. Paper and pencil (pen) a. Write things down to remind you, categorize things, you can do all sorts of stuff. b. Draw, make it up quickly, written hard copy, plan, play with options, you can flip pages, you can have huge, tiny massive, erase, mobile, searchable. c. Limitations – Search-ability but not centralized. d. You have to have it. Potentially dangerous with loss or damage – outside sources or personal neglect. e. Not centralized – no one else has it. Hard to share unless you send or copy it. f. Only one original. g. Break pencil and paper – searching, stacking, organizing, auto calculate, create relationships, nothing is automatic, everything is manual. h. Physical problems with paper, run out of ink, pencil breaks, if you lose the original, you have to start all over again. i. As it spreads, it becomes harder to get back to what you are looking for. No record of who touched anything. What date/times some things happened. 3. Computer Based – word processing or a text document a. All the creativity of paper and pen but you can now search it, print it, save it, send it, centralized, easy access, looks nice, readable, formatted, spell check, copy & paste, speed. b. Graphics, links, insert things, create columns and rows, email it, go back and change (small amounts to full pages of new content), take things away (delete). c. Limitations – structured, certain rules, learning curve (learn the tools), the program itself (does it even offer what you are looking for). d. Your skill level. Electricity and a computer or device. Dishing off to outside sources (printers, faxes, email, Internet). e. If it is not centralized, it doesn’t do anybody any good. Run out of space to save it. 4. Spreadsheets (rows and columns) a. It does the math for you. It can do calculations. Searchable, organize it, show/hide columns and rows, color, graphs, add graphics, block in cells, lock cells, connect certain things. b. Ability to reference to specific cells. Ability to sub divide and expand. c. Good structured look and feel. d. Export and Import data because it is already formatted in rows and columns. e. Changing sizes and merging data cells. f. Limitations – volume. It maxes out at a certain level. g. No history – once you replace it with something, it is gone. h. Higher skill level in order to play. i. Limited to rows and columns. j. It is not centralized. It is on your machine. k. Static layout – If your data is different or variable, it breaks. l. Break a spreadsheet – volume, you have to see the whole thing at once. m. Formulas and moving and inserting columns and rows. It may break all of the formulas and references to other cells. n. Electricity, computer, you have to buy it. o. Spreadsheets are not the most compatible for touch screens. p. Manual filters and always looking at a full screen of data. You can get lost very easy if the columns and/or row headings are not shown. q. You can overwrite things very easy. 5. Databases a. Unlimited structure, storage in the billions, relationships, histories, you can link things, search things, you never look at the whole database all at once. b. Return and report, call back, dynamic level for storage (one-to-many). Scalable. c. Different types of databases. There are file share databases (limited number of connections) or server databases (unlimited number of connections). What are the open connection options. d. Calculations, filter things, pull back certain rows, you can query things (asking it for things), loop or play in bulk – multiple tasks at once. e. Storing and cataloging things. Modular or ability to compartmentalize. f. Limitations – Where is the database located at? Location is very important. g. Computer problems such as electricity, hardware issues, connection issues, multiple variables. h. Security issues. i. Skill level – who sets it up? Who is going to work on it? How easy is it to get the data in and out? j. Break a database – volume (usually traffic vs. size). k. Deleting or dropping information. Losing integrity between pieces of the one-to-many. l. Too big or cumbersome. 6. Software Packages and IT (Information Technology) a. Package or packaged. Pre-built, on your own computer. Industry specific scope or niche. b. Keep coming out with new upgrades or versions. Improvements are being made. c. Thousands and thousands of choices. d. User friendly (general statement), support, manuals, well used and communities, training, etc. Lots of resources. e. You feel like you own something – even if it is older – you still own it. f. You can customize it for yourself. Create you work flow. g. Networking and everything can be hard wired. Established different connections. h. It is a tool that is meant for a specific job. It is a catered tool box. i. It has a version number that related to a historic level of the software. j. There are freeware, shareware, and different pricing structures. Bundles, packages, suites, downloadable or on a hard copy (disk). k. Limitations – price or cost. Same with IT (information technology). $0 to millions and millions. l. Implementation and delivery. How do you get it? Install? Download it? Served up to you? How do you consume it? m. Versions and computers – they don’t always match. Upgrades. Static and constant need for upgrades. Once you make it, it is that version until the next upgrade. n. Licenses – how many do you have and how many do you need? Bottlenecks of limit output by not having the right tools. o. Niche specific – but then you have to try to marry non-compatible products together. The average is between 4-6 software packages. Maybe more. p. Skill set and use of the tools. q. Break software – viruses, outdated, cost, volume, traffic, and hardware issues, not support of non-user friendly, natural disasters, computer crashes. r. Newer products with more features. Constant leap from of features. 7. Web & Cloud a. Great when it is fast, personal, anyone can access it with a device, centralized, unlimited as far as storage capacity, versatile. b. Use outside pieces, tons of features, graphics, links, form, buttons, animations, video, sound, print, you can search like crazy. c. If hardware crashes, no problem, switch device. d. Cut you IT (information technology) costs to almost nothing. e. Mobile. From your car, on the go, multiple things connected to the same pieces of data, collaborate from anywhere, anytime, multiple people can share tasks and work on projects. f. Conditional logic (if, then). NO updates, no waiting for the next upgrade (it gets pushed to the server). g. ADILAS – All Data Is Live And Searchable, Secure, Serviceable, Scalable, Sustainable. h. Go paperless. Scans, images, files, and other content tied into the system. i. Skin things (look and feel and flow and processes). j. Cut steps, speed up processes, customize things to a huge level. k. Younger generations are getting more and more tech savvy. l. Future??? Where is it going? Currently pioneering some of these fields and places. How deep is the rabbit hole? Potential! m. Limitations – Have to have Internet access (somewhat of a diminishing problem). More and more places are getting it and access is becoming free more and more. Free is good! n. Travel if Internet is down – have to get to a signal. o. Security or un-secure (hacks and stolen data). Semi unknown??? Brings up question because you don’t physically have it or can’t touch it. Where is it? Movies almost create this hype or scare on vulnerability. p. How adilas.biz uses security – HTTPS – the “S” is very important. This deals with a thing called SSL (secure socket layer) – encryption. Check logins – 3 strikes you’re out policy on failed logins. Each corporation (aka virtual world) has users assigned. Each page in the system checks for a three-way tie or code. Corp to User – User to Permission on each page. System history or virtual surveillance system. 75% of the entire adilas.biz application deals with validation and security. q. Skill set – certain requirements. r. Interoperability – meaning playing with outside players and service. Everything has to work together. Adilas – uses a “System Thinking” type model. Cause and effects, consequences, tell the story, connections and relationships. s. Custom needs. Load balancing and potential traffic. Adilas tried to be an e-Business buffet – you dream it up, we’ll wire it up! t. Play with both old and new technologies. Browsers, computers, operating systems, unknowns. 8. API or Custom (application programming interface) 9. World Building (stories and movies – ultra custom level) |
|
|
AU 1786 |
|
Daily Tasks | 9/25/2013 |
• More emails and light tech support. • Went in to town for day two of the September adilas training course. My sister and I started the day back on the brainstorming document and talked about other tools and features. Build and break, build and break. WE then played in a sewing shop and covered customers, elements of time, flex grid, and eCommerce. Great session and we dipped into all of these options in good depth. I enjoyed the day and training session. My sister and I talked about how elements of time is somewhat of a foreshadow of things to come. This includes creating master template, point and click options to add/edit features and functions, different report types (calendar, time slot, grouped, and details), advanced search options, etc. Lots of similar options to what we want to do with the rest of the application. We want to take it to the platform level. 30 miles. • Emails. Trying to keep on top of things. |
|
|
|
AU 2147 |
|
Adilas 3 Day Training Notes - Logan | 9/25/2013 |
Day 2 – ***Making an Excel template so that people can get their data in as fast and efficiently as possible. -Flex grid must have a host piece of the puzzle; it doesn't exist just on its own. -Adding flex grid in bulk - will be a really neat tool -So many neat ideas to come - so how do we help things move along the most or take off what load we can take off the developers so they can work on these custom projects -COOL stuff coming with Elements of Time - like being able to balance or track anything you would like in adilas.... to the time slot level... like being able to see to the hour when you went out of balance... or be able to track when you have your highest times for invoicing... basically to be able to pick and see anything you want at the time level... super COOL! -Time & mapping - where does it start, what are they key points/times, what needs to be mapped back to -Idea from Joe: Create a color "key" code for what you have color coded for your elements of time - really that would be best done as the business creating it for themselves and what they have their colors tracking as.... but you could possibly have a way to list what colors they have assigned to what templates... or maybe just have the colors show up when you are on the add/edit/view time templates page... -API - consume as needed and as desired |
|
|
AU 1787 |
|
Daily Tasks | 9/26/2013 |
• Went in to town for day three of the Logan training class. Once again my sister and I worked on the “tools that we use” brainstorming document. It covers these tools: 1. Head & mind 2. Paper & pencil 3. Computer based – word processing or a text document 4. Spreadsheets (rows & columns) 5. Databases 6. Software packages and IT (information technology) 7. Web & cloud 8. API or custom (API = application programming interface) 9. Virtual world building (like stories & movies – with characters, relationships, trouble, decisions, and consequences) • After that, we got in to deposits, bank stuff, and lots of theory about how adilas tracks the data. We talked about auto vs. manual. We also talked about flow and natural cause and effect relationships that exist as you advance the ball from holding area to holding area. Just like water slowly transforming to slush, snow, and then ice. I used my marker pen quite a bit to explain and demo different scenarios. In the afternoon session, we had another guy come participate with us. He is looking into the assistant web develop position for adilas. He was quite sharp and seemed to follow along well. After the class, we conducted a formal interview. He seems to have some great skills. He also seemed to be very stable and a natural leader. Good stuff. As another comment for day three – I spent a good half an hour showing history and how adilas runs things on a more modern model and method. I had fun with it. |
|
|
|
AU 2148 |
|
Adilas 3 Day Training Notes - Logan | 9/26/2013 |
Day 3 – ****-Potential fix-it: when we turned off the start cart permission, and even other permissions, it was still able to get at the start cart page and go through the cart. **** *** You dream it up, we'll wire it up! What information/data do you want to track? Such incredible capacity for tracking data like crazy!!!! What happens... normal day to day transactions or "accounting" of what you have done... what you want to track -This is a live, experimental, real time project... not a software package wrapped on the shelf at Wal-Mart... But there is huge potential & flexibility with that. -Eventually people will end up building similar systems to adilas and tracking data and things this way. -Consultant: When people get data, they want more and they want it faster &... &... & -Mapping back because the object is moving over time - so you don't have to enter debits/credits, etc., etc. -Net profit from P&L goes right to Balance Sheet. Balance sheet where you eventually want everything to flow... balance sheet - a picture in time - point in time, am I in balance? P&L flows over time... length of time... net profit flows into (an equity on) Balance Sheet. ***We NEED or should create - that graphic/flyer, however you'd like to show it of the difference between T-accounts and how technology has improved to track things over time and map back and track everything -Web services and eCommerce - 3 letters of company and corp key id (i.e. mor-03 or use-53) to get into the shop eCommerce - go to the home page of adilas and add shop after the backslash, then put in the corp id - the use for testing playground: guest, 1234 -Once you know what containers you have put things in... then you can jump to them super fast... you know which drawer or container to go to, to find what you're looking for... -World building: characters relationships, trouble, decisions, consequences .... cause and effect |
|
|
AU 1788 |
|
Daily Tasks | 9/27/2013 |
• Emails and light tech support. • New logo for a company. Posted logos and colors online. |
|
|
AU 1789 |
|
Daily Tasks | 9/28/2013 |
• Woke up and recorded a couple pages of notes about where we want adilas to go. I was writing and writing for almost an hour. Good stuff. See the notes later on. • Recording notes in my notebooks about the past couple of day and some of the training topics that we covered. • More notes in my notebook. I was pretty sick today. It’s been a rough day. It is interesting how fragile we really are. |
|
|
AU 1803 |
|
Daily Ideas | 9/28/2013 |
Random notes – Woke up 3:30am and couldn’t sleep: - Use graphic mock-ups and layouts. No code is required and a picture tells a thousand words. Super-fast and it creates a model or goal to build towards. - Make graphic flow of different pieces. This could even be simple flow charts. - Use existing pages as default icons. - Get notebooks to my sister and get caught up on what is in the notebooks. - Help Steve push the adilas world to a real usable level. - Maybe think of small trial periods for approved persons. - I need to do more teaching and training. This could be in ColdFusion, adilas, or adilas sales and service. - Check out the operations seminar at USU. What a great resource. - I need to play as a team instead of just doing things all by myself. - Contact my brother and work with him on some of his commercial ideas and what not. - Get creative on funding and money flow. - Figure out new projects, scopes, and budgets. - Go back and review notes from 12/24/12 (December of 2012). Lots of good notes and ideas. - Figure out what is promised as far as tools and features. - Schedule the next training event. - Post the first round of the user guide. - Recruit internally. - Put Shari on task with the user guide. - Adilas university may end up being a non-profit. Until then, go ahead and just run it as it. We can transition later. - Get the database ready to be duplicated. - Finish up tools and features for eCommerce. - Get the content server up and online by end of 4th quarter 2013. - Organized and prepare the next whole level. Take adilas to the platform level. This is us dreaming to a super high level. Reach and stretch a bit. As a note, plan that this next level or model, at some future point, will also break and become a stepping stone. Include: custom css, layout, design, destinations, flow, tables, code, choices, in-line custom code, API options, pre-built templates, pattern after elements of time with build your own types and apply functions as needed. Be able to create your own flow and check points. Think of holding areas, checkpoints, permissions, and flow. We also need to add correct data mapping back to states and status and holding areas. Track the full life cycle of the items and transactions. - You dream it up – we’ll wire it up! - Show flow charts. This could be recommended flow, options, and special circumstances. - Use other people’s money to fund the projects. - We bring experience and vision to the table. - We will build on what we have. - The new platform level may need steps, phases, and different levels. - We at adilas need to follow our own advice and dream it up! - Document it, sketch it out, draw it up, and go to it. - Make visual homepages with icons and sections. - Get the notebook caught up… It takes extra effort to do things twice. Writing and sketching and then rewriting. - We have been planning this upgrade or next level for years. This doesn’t just come out of nowhere. - Think “platform”! Think “world building”! Think “in-line custom code”! - Make things consumable! - Plan the education and training from the get go or right from the start. This can’t be an afterthought. You almost plan it from the beginning and let it lead development. Then it truly becomes marketing. - The project for the developer’s notebook is very important. We have to share and communicate what is going on. This notebook is a huge part of our communication and direction. - Plan it out, seek help, use other people’s money to fund the projects. - Our plan is to share and seek protection out in the open by sharing. We also want to focus on the abundance model. Not only is there enough to go around, this model deals with more than money and business. My sister said the other day, this model also deals with people, skills, ideas, talents, drive, etc. Her saying that really helped my open my mind and think differently. -Start with education and an open API (application programming interface) or open source code. Those are two huge keys that we currently have shadows of but are lacking the full implantation of those features. - In order to get where we are going… You have to have some time in the game. - Education needs to be brought up to the marketing level. -We may end up leap frogging ourselves. That would be kind of fun. - Build to eliminate bottle necks in flow, processes, code, education, marketing, people, and other pivotal points. - We want to get marketing involved from the ground floor level. - On a personal note, I’ve done a number of projects and tried to market after the fact. That process is pretty tough. We need to see the vision and fund the projects with the vision. Self-funding is very difficult. - Plan for mobile and new technology! - Plan for data production and duplication! - Plan for snap-on and bolt-on additional features. It would be super cool if some of the code and features already anticipated external connections. Think application flex grid level. - Depending on our goals… we might need to start a whole new company or at least another arm of the current company. - Talking about new or extending business can be scary. It feels big! But, we’ve done this before and , most likely, we’ll do it again. - What about timing for this? That is still kind of a big unknown. - I am sad now. Sitting here thinking about the size of the project that we are currently in and thinking how big this current proposal is. In order to build, the weight, load, and wealth must be spread out. And then I start thinking... Build on what you have! And, the mode softens. I need to remember that saying. - Use adilas' existing base and experience to market the next level of growth. Again, build on what you have! - As an idea... I know of a company with a dream and they are daily building towards it. Would you like to hear more or become a part of that vision and dream? The company is called "adilas.biz". Come and check it out! - The taboo word is not "break" or "break it". The real taboo word is "eventually". This came from a small conversation during one of the lunch breaks during the Logan September adilas training course. - Choose your flavors (like an ice cream shop). - Pick your tools (like a tool shed or toolbox). - Skin your engine (like a vehicle). - Build your world (like worlds of a solar system). - This might be a fun part of the adilas formula flyer. Maybe replace the results section of the flyer. - Sample sketch of this idea (see photo gallery, sketch includes: Choose your flavor (ice cream treats), Pick your tools (tools for building), Skin your engine (different vehicles), Build your world (different worlds and planets), adilas logo in the middle. |
|
|
AU 1790 |
|
Daily Tasks | 9/30/2013 |
• Answering emails and light clean-up. • Emails and tech support. Writing about oversized images for a company. • On the phone with Steve talking about customer reward points and how to tie-in custom scenarios to the actual shopping cart. Great conversation. I’m really proud of Steve. He planned some of this project clear from a paper and pencil level. • Went in to town to meet with a student for his adilas interview. I offered him a job to help with training flow and mapping out different parts of adilas. He may also help with light computer tech stuff. Good interview. 30 miles. • Went to BATC and check on the September training footage. Spot checked a number of video segments. • Went to Smithfield to work with my brother on new video clips for the August training. • Emails and tech support. Answering questions on balance sheet items. • Customer upload for a client. |
|
|
AU 1804 |
|
Daily Ideas | 9/30/2013 |
-We need to officially offer the positions to the interns that have been interviewed. -We have had request to make the balance sheet in to a system generated PDF document. -Recruit trainers for the October training session. -Send out emails for interns that didn’t make it. |
|
|
AU 3642 |
|
To-Do & Brainstorming for the Teacher Site | 9/30/2013 |
To-Do’s - Customer upload for a client - Recruit trainers for the October training session - Send out email for interns that didn’t make it - News & updates – October adilas training pdf flyer - Send out email for ColdFusion class - Print out more business cards - Do the Teacher stuff - Update YouTube & adilas university site with new files - Put all help files or at least give access to them from adilas university. Maybe even allow people to see the developer’s notebook. - How can I help and get the biggest bang for my buck? Help videos, user manuals, graphics, code, selling, coordinating? Interfaces, mapping, flow, flyers, commercials, documents, training? Brainstorming layout for forms on the teacher site: (Please see scan in photo gallery) |
|