Adilas.biz Developer's Notebook Homepage

[reset this page] . [historical web outline - entries by month] . [adilas community funded projects] . [contact adilas.biz support - email form] . [help]

Search The Adilas.biz Developer's Notebook
Time Period:	Daily (enter the day you want to see) Monthly Custom Date Range to
Template Filter:
Color Code:
General Text Filter:	(use a plus "+" sign to separate search terms. ex: jack+jill+hill)
Sort Value:

Adilas.biz Developer's Notebook Report - 2/1/2013 to 2/28/2013 - (36)
Photos	Time Id	Color	Title/Caption	Start Date	Notes
	AU 1076		Daily Tasks	2/1/2013	• Emails and tech support.

	AU 1077		Daily Tasks	2/2/2013	• Emails and tech support. • Updating help files for the flex grid.

	AU 1078		Daily Tasks	2/4/2013	• Emails and tech support. • Updating help files for the flex grid. • Other help files and buttoning things up a little bit. • Helped my wife with some ideas for training graphics. We then went around and took training flyers to some contacts. • Working on other help files and cleaning up from past projects.

	AU 1100		Daily Ideas	2/4/2013	-We may need a technical overview for clients that want to know the technical side of adilas. What OS, platforms, encryption, database models, scripting languages, back-ups, recovery plans, etc. This could also be hosting, networks, system requirements, dependencies, hardware options, add-ons, etc. This idea came from a rep. -We need a bulk create statements. We also need a bulk print statements. -Bulk tax category flip on the view cart page. If more than three items, show a link. The link would just add a master chooser for the tax category. Once clicked it would update all tax categories on the cart. Ended up adding the feature right to the view cart with some Java Script to help flip in bulk.

	AU 1079		Daily Tasks	2/5/2013	• Emails. • Got a call and someone had been in to the models database and had created a problem and changed a bunch of stuff. I had to find an old database copy and create a function that did a copy and paste from old to new models. If this continues, we’ll need to implement a hidden models and makes history section. We won’t show it to anybody, but we will capture and store who does what. • Quick tweak to the add/edit help file page. • Added a view link as an option for each help file. • Working on the main add/edit expense/receipt help file. Lots of good information. • More help file stuff for expense/receipts and explaining “splits” and payments on account.

	AU 1101		Daily Ideas	2/5/2013	-We need a hidden table for makes and models. Along with this, we need to monitor name changes and who is doing it. These two sections run on a global table but we need to monitor who is playing in the tables. -A database table called “models copy” was put into the main database. It was used to copy old model names across to the new table where somebody was messing around. When the dust settles, we need to remove that table at some point. -It would be very cool if we could use the interactive map and allow users (say at a trade show or just in general) to click on an area and then be taught about what goes on in that area. -The term ”splits” – it deals with payments on account. What it really deals with is how adilas virtually splits a bigger payment into smaller details to satisfy the smaller sub expense/receipts. A good analogy is ordering lunch (a few different people) and getting individual checks. The boss comes and decides to cover all of the individual checks. This creates a one-to-many relationship between a bigger master expense/receipt and smaller sub expense/receipts. The splits come into play as we use the master to satisfy the subs and create the new relationship. Another analogy – multiple invoices making up a statement. -It would be really cool if you went to a section in adilas and it showed options for what was there… a visual map to the different parts of the layout and flow.

	AU 1080		Daily Tasks	2/6/2013	• Recording hours. • New logo for two companies. • Wrote an email explaining differences between print and online viewing. • Research on Java Script jump menus. • Prepping for a new bulk flip option for tax categories inside the shopping cart. • Working on a master tax category switch for the view cart page. • Finished up the bulk tax category flip options. • Sent an email update to a client. • Posted files online.

	AU 1081		Daily Tasks	2/7/2013	• Emails and tech support. • Working on the shopping cart help file and other emails and tech support. • On the phone with Steve. We talked about training, payroll, new clients, custom work, eCommerce and tons of other subjects. We talked about a need for new PDF flyers for pricing, tech specs and rep docs. How much things cost? What is required? And how we pay? We also need a what is our business model? We also talked about outside funding sources, future server needs, etc. Great phone call. • Working on the shopping cart help file. Major rework. I didn’t realize what a major piece the shopping cart is. It is the interface between customers and the whole rest of the system. Almost everything else hinges on that piece. • Finished up the help file for the shopping cart or the view cart page. Huge overview.

	AU 1102		Daily Ideas	2/7/2013	-I’d love to create a graphic that shows how important the “shopping cart” is to the system.

	AU 1082		Daily Tasks	2/9/2013	• Help files for the shopping cart.

	AU 1083		Daily Tasks	2/11/2013	• Reworking the help files for the shopping cart. • Rep flyer and tech support. • Research on POS systems. • Working on a career opportunities flyer for adilas.

	AU 1084		Daily Tasks	2/12/2013	• Working on a career opportunities flyer for adilas reps and consultants. Sent a rough draft to a few people for feedback. • Working with my wife on editing the career opportunities document. • Small logo change for a company. • On the phone with Steve going over business and new developments. • Working with my wife on the career opportunities flyer.

	AU 1085		Daily Tasks	2/13/2013	• Bank stuff and monitoring images. • Working on the career opportunities flyer.

	AU 1086		Daily Tasks	2/14/2013	• Reviewing the rep flyer document. Sent a copy to my dad and Steve. • On the phone with a client, they had a number of crazy internal trades, deals, pass through items, etc. We walked through each internal deal. As we went through, we used the flex grid to tie the pieces together. • Final editing on the career opportunities flyer.

	AU 2272		Brainstorming - Pricing Flyer	2/14/2013	Pricing flyer - Graphic of the map and different parts and what their acronym is (POS, CRM, BI, etc.) (full one page graphic) - Piggy back system - Feed the independent reps and consultants - Show averages and sweet spots - Charge for custom work - Keep it open - Plug the reps (feed the program again & again) - Volume, usage, storage, locations, employees, processes, stock/units - You get it all… - We reserve the right to contact you if we see abuse or miss information on how you’ll be using it - We have a report that shows us counts and totals - Custom and onsite work setup, training, consulting - Credit card – payment options: monthly, quarterly, semi-annual and annually - Multi corp discounts - No contracts, no other required fees, open model… including using independent reps and consultants IT or Tech doc - Photo of a full standalone system with a price tag and a big x through it… then show options and how simple it can be… make it kind of fun and a no brainer.

	AU 1087		Daily Tasks	2/15/2013	• Tech support and calling Steve. • On the phone with Steve talking about options and possibilities. • Emails, phone calls and tech support.

	AU 1088		Daily Tasks	2/16/2013	• Emails and tech support. Adilas had some problems today (resets and memory issues). • MySQL tech stuff. • On the phone with Newtek talking about MySQL memory settings.

	AU 1089		Daily Tasks	2/18/2013	• Checking stats on the remote server. It looks like a maxed out hard drive… Maybe a simple new hard drive will buy us some time. Split the ColdFusion and images on one drive and the MySQL database on another. • Checking and cleaning out some old files on the server. • On the phone with folks from Newtek talking about servers. • Emails and phone calls. • Printouts for class.

	AU 1090		Daily Tasks	2/18/2013	-From 12:00pm (noon) on 2/18/13 to 2/23/13 at 10:00pm the adilas team was in town. It was so crazy, no records were written down. This is not a play by play record but here is a recap. -Got a call from Steve. Went and picked up the adilas team (4 others including Steve). We drove around town and had lunch at San Francisco Sourdough Pizza. We came home and got people settled in. We had a number of little meetings and brainstorming sessions. We ate dinner and then did more work. On the evening of 2/28/13 we shut the server down and they (Newtek) did a hardware update and installed a new hard drive. We were up past 12:00am, midnight, every day of the week. 30 miles.

	AU 1091		Daily Tasks	2/19/2013	-Super early in the morning 2:00am-4:30am Steve and I (Brandon) got the server back online. We woke up and then got ready for day 1 (one) of the first adilas.biz training courses. We met at Bridgerland and set up the class. We had a number of students who participated in the class. We also had a guy who watched via Skype. We went from 9:00am-5:00pm with an hour for lunch. Adilas bought the lunch for the students. My dad videotaped all three days of training. After class we ate dinner at my house and talked and had little light meetings. Steve and I worked on his developer laptop and getting everything installed and up to date. To bed after 12:00am. 30 miles.

	AU 2273		Note - Quick Search, Systems Thinking, & Permissions	2/19/2013	- Quick search – “Help files” o Bullets o Alpha o Bold o TOC – “Table of Contents” - System Thinking (cause & effect) - On permissions o A preset list of permissions

	AU 1092		Daily Tasks	2/20/2013	-Day 2 (two) of training. We woke up early and did a few things and then off to class for the day. 9:00am-5:00pm in class. My dad videotaped the whole day. That night after dinner, we had a meeting about what we need to do and where we want to take adilas. My wife participated in this team meeting. 30 miles.

	AU 1103		Daily Ideas	2/20/2013	Rough notes from our team meeting on 2/20/13: -For our business – we need to know data stats, values, amounts, etc. How much? How many? How often? -What are the market indicators for us? -Sub out the code building of custom pieces – or open up the “API” (Application Programming Interface) for others to use. -Emails – not others with an adilas address. Have our reps keep their own email addresses. -Minimal bridging of reps and users. -Revamp the salesperson commission calculator. -More validation and the known issues page. -Page by page validation. -No more collecting setup fees for reps. Keep things at arm’s length. -$100 per hour for adilas training, consulting and setup. -Tech support – free up to 15 minutes – charge after that. Maybe don’t focus on the time amount – what is the nature of the call? -Lay some things out so that everybody plays within certain rules or levels. -The reps and what they serve – open field. -Use the flex grid or admin (hidden) corp-wide settings to map corps to clusters. (Cluster idea: content server - number of data servers) -Load the deal – prep for the next sale. For example: your rep will be giving you their fees. -Note in the Tahoe – Use the monthly accomplishments as the base for the developer’s notebook. Treat it like a drill-down *-Systems thinking – huge concept! -Create or start towards the dream system and how the structure will go. -Play as a team! -The definition of a rep or a consultant is very loose. Basically, it is someone who knows something about adilas and is willing to share and teach. -Think modular data. Move, balance, delete, harness, pair up. -Excretory (waste) system – we need a way to get rid or purge waste. -Think about Newtek – they have tons of servers. Some shared, some dedicated, etc. Think at that level. -Show dynamics of the system. -Let the customer set their own value (what is it worth). We could then come back and say what we think. -At first, until we get some historical data, we need to make an educated guess on price and service levels. -Review or possible review every 6 months. -Pricing for each client is based on industry and usage. Basically, customized for each business based on type or size. -Pricing is also based on habits (usage patterns). -Every client is different. -We may need to cut and snip. -We do have access to total usage and stats. -Pros and cons – comparison charts – list of features. -Web-based and software enhanced. -We want an API and full business platform. -XML, web service, some other format.

	AU 2274		Brainstorming - Meeting to Talk About Adilas	2/20/2013	- For our business… we need to know data stats, values, amounts, etc. How much and how many of this and that? - Market indicators for us. - Sub out the code building… Meeting to talk about adilas: - Emails – not others with an adilas address - Minimal bridging of reps and users - Revamp the salesperson commission calculator - More validation and the known issues page - Page by page validation - No more collecting setup fees – arm’s length - $100 per hr. for adilas training, consulting, setup - Tech support free up to 15 minutes – charge after that - Lay something out so everybody plays within certain rules or levels - The reps and what they serve – open field - Use the flex grid or admin (hidden) corp-wide setting to map corps to clusters - Load the deal prep for the next sale (your rep will be giving you their fees (Note in the Tahoe) - Think modular data. Move, balance, delete, harness, pair up. - Excretory (waste) system - Think about Newtek… They have tons of servers, some shared, some dedicated, etc. Think at that level. - Show the dynamics of the system. - Let the customer set their own value (what is it worth). We could then come back and say what we think. - At first, until we get some historical data, we need to make an educated guess. - Review or possible review every 6 months - Pricing for each client is customized based on industry and usage. - Based on habits (usage patterns) - Every client is different - We may need to cut and snip - We do have access to total usage and stats - Pros and cons – comparison charts – lists of features - Web based and software enhanced o We want an API and full business platform o XML, Web services

	AU 1093		Daily Tasks	2/21/2013	-Day 3 (three) of training. My dad taped the whole class and we were at it from 9:00am-5:00pm. At the end of the class, I showed my mom specific things that she had questions on. We spent three good days and only touched on 25% of the application. That was an eye opener to quite a few of us. More good stuff to come. 30 miles. The adilas team was planning on leaving sometime on Thursday the 21st of February. However due to snow and weather, they ended up staying until Sunday morning. Those extra days were a blessing to me and my family. We got a lot done and were able to talk about a number of different topics and items.

	AU 1094		Daily Tasks	2/22/2013	- Random different activities and somewhat unstructured day.

	AU 2275		Brainstorming - Meeting to Talk About Adilas	2/22/2013	- The servers are the top monsters. Cluster: content, data 1, data 2, data 3, adilas university, web services, outside website (sketch of flow and layouts – see sketches in photo gallery) - Put the help files on adilas university - Put YouTube videos on adilas university - Put the developer’s notebook on adilas university - Monitor each cluster and who is on each server - Growth and “farming” of data and servers - Keep cluster 1 and data 1 very small and make adilas the controlling entity - Play musical chairs – mix and match – learn other pieces of the puzzle

	AU 1095		Daily Tasks	2/23/2013	- Weather was still bad. We went over to my parent’s house and watched some of the training footage. After lunch we had another great adilas team meeting. Here are some notes from that meeting.

	AU 1104		Daily Ideas	2/23/2013	-“It’s time for musical chairs… everybody get up and go to the next station.” -S.O. -“Are you prepared to let go of what you need to?” –my dad. -With reps – do’s and don’ts. With paying – do’s and don’ts. -What do we need to setup a corp – process or required pieces. -Adapt and overcome! -Outline and structure the training material – we were a little too open. -Bank account to get ACH services. -Take off the flyer about bringing the lunch. -The servers are the top monster. -(Sketch in notebook with clusters. Content - Data 1, 2, 3, etc. - each corp has its own little area - each corp feeds the outside web services (adilas web services). If content is needed it gets pulled from a content server. (Adilas university)) -Sketches of the cluster model. -1 content server hooked to multiple data servers. -Each data server would have a number of corporations under a specific data server. Kind of like their own little “adilas”. -The model above is for a single cluster. Multiple clusters could be used either together or by themselves, very flexible… -Put the help files on adilas university. -Put the YouTube videos on adilas university. -Put the developer’s notebook on adilas university. -Monitor each cluster and who is on each server. -Growth and “farming” of data servers. -Keep cluster 1 and data 1 very small and make adilas the controlling entity. -Play musical chairs – mix and match – learn other pieces of the puzzle. -Accounts are reviewed on a semi-annual basis. Based on that review, we analyze and will do something with the monthly fees. -Create a web-based company assessment. Fill out as much as you feel comfortable: looking for numbers and values. - # of EIN’s - # of Location(s) - # of Employees - Business type or industry - # of transactions - You get it all…. Help us know which features you are interested in? o Do you have inventory? - How many unique types? o Do you have any serialized inventory or big tick items? o Do you sell labor? o Do you sell time? o Do you sell services? o Do you plan on uploading photos, scans and images? o Do you plan on using the scheduler and elements of time? o Do you plan on using merchant processing? o Do you plan on using eCommerce? (May require additional fees) Still dealing with a web based company assessment… - Other notes on request - Reps or how did you hear about us - Main contact info - Company name - Contact name - Phone - Email - Call to action! -Have the reps use this request from to submit info to us. This would be how they request a new corporation. -Buttons that say “quote me” or “sign me up”. This is a call to action or an action link. -We will be contacting you. -Have and show some testimonials. -Having the adilas team here in Utah at my house was a great blessing and we got a ton done. I’m super thankful for a couple of extra days due to bad flying weather. It was a blessing in disguise!

	AU 2276		Brainstorming - Meeting to Talk About Adilas	2/23/2013	- Accounts are reviewed on a semi-annual basis. Based on that review, we analyze and will do something with the monthly fees. - Web-based company assessment (numbers and values) – fill our as much as you feel comfortable o EIN’s o Location(s) o Employees o Business type or business industry o # of transactions o Which of these features are you interested in • “You get it all” • Do you have? o Inventory types and counts (how many) • Unique items • Serialized • Non-serialized • Labor • Time • Services o Other advanced options: • Images/scans photo uploads • Elements of time • Merchant processing • eCommerce o Other notes or requests o Reps or how did you hear about us o Main contact info o Company name o Contact name o Phone o Email - Have the reps submit info to us. Request a new corporation - Buttons that say “quote me” or “sign me up” (“action link”) - We will be contacting you - Testimonials - It’s time for musical chairs… everybody get up and go to the next station. (Shari) - Are you prepared to let go of what you need to? (my dad) - With reps – do’s and don’ts o Paying do’s and don’ts - What do we need to set up a corp – process or required pieces - Adapt and overcome - Outline and structure the training material… we were a little too open - Bank account to get ACH services - Take off the flyer about bringing the lunch - Global updates o Creates and updates take longer o Reads are faster o In loops (batch transactions) wrap in transactions or rollback recovery options. o The database should be the base model o “Linked in”

	AU 1096		Daily Tasks	2/25/2013	• Bank stuff and cleaning up from last week. • Cleaning up office and cleaning up from the class. • Logos and quick tweaks. • Uploaded the retail dashboard interface. • Changed the bulk move PO’s page. Changed from checked to not checked by default. • Added a select/deselect checkbox to the bulk move PO page. • Posted files online.

	AU 1097		Daily Tasks	2/26/2013	• Working on logos. Did five new logos and colors. • Calling some folks to let them know about the retail dashboard. • Help files and did a small screen capture of the retail dashboard and put it up online as part of the help file. • Research on barcodes on PDF’s. • Cleaning up office and going over old brainstorming documents. • Recording hours from loose pages to my notebook.

	AU 1105		Daily Ideas	2/26/2013	-Break things into types and functions. This could be any of the main and/or sub players.

	AU 1098		Daily Tasks	2/27/2013	• Writing an email to the Newtek server team about options, load balancing and growth options. • Research on MySQL and how best to configure the engines. Called and talked about MySQL and ways to make it be more effective. • Research and phone calls to MySQL salespersons. Reading up on MYSQL 5.G. • Recording hours from loose pages to my notebook.

	AU 1099		Daily Tasks	2/28/2013	• On the phone with a client going over options for custom websites and eCommerce. Sent them an email with info on what we have already got in place. • Working on new schedules for classes and training. Called Bridgerland and also called my sister to see is she could help me with using “go to meeting”. • Online viewing videos for go to meeting. Browsed their site and watched a number of video clips. • Got scans ready for a member of the adilas team to help with a pricing matrix or fee guide. • Purchased a one year license of go to meeting (Citrix online) to help with training events. • Recording hours in other notebook. • Quick phone call to Steve and playing around with go to meeting tools and such.

	AU 1106		Daily Ideas	2/28/2013	-Modular, white label, resale, custom code via API, login by corp-id and then username and password. Each cluster could be 100% independent. All of the independent’s report back to the master. Versioning, saving update files, be able to tell what version a server or cluster is running on. -Set a master corp per server. That corp could administer things on that box. -Virtually set up a chain of command. -Setup (maybe even beforehand) database shells, data sources and then record settings back to the master. -Security may get interesting – do what we can and move on… we don’t live in a bubble. -Support and manage changes. -Be able to pull stats and do admin updates on remote servers, clusters or standalone stations.

What's New

Products

Find Us