Got on a meeting with Russell just to get him some server log files. He is going to be parsing them and building a tool to pull the log files apart (one of his class projects for school).

Anyways, as we were downloading logs and what not, we ended up striking up a conversation about the adilas model and how things were working. I took a whole other page of notes, see attached. Lots of good stuff. No immediate answers, but openly talking about things and where we want things to go. Steve ended up joining us once we got part way through our meeting. Totally impromptu type meeting, but some good things.

Part way through the meeting, I merged in some code for Steve. We also talked a lot about managing starts and stops (transitions on code projects). That is tough to manage some times. Here are some of the other notes.

Good things...

- Lots of projects coming in with funding
- People want what we are doing

- Limited number of devs
- Some don't like mmj projects
- 2 guys that are designers
- Few project managers

- We don't need more normal developers... we need more mmj developers (currently)

- Smart enough to work on their own but be able to understand

- Project manager and product manager on mmj side
Steve, Dustin, Eric, Spencer, Danny, Bryan, Jonathan Wells

- Here's our problem... how can we get people in and working on those projects quickly
- Not shooting for the best model... but enough to help it work and function

- We are looking for people who are willing to play how we need them to play
- There is a different team that is working on r & d and new code

- Laser focused training to get them up to speed.
- Training for existing developers (already trained but just switching syntax)

- The core system needs to be separate from the business verticals that are built on that core

- Every business vertical needs its own team/manager to really help it play together

- Lift where you stand... take care of your space

- If you get teams that just deal with specific verticals... they become productive in their space - cover your zone

- Trying to keep developers in their flow... the transitions (starts and stops) kill and drain the energy

- Working overtime vs more people working part time - Steve used to do this in the car business

- Managing those resources and making sure we are paying for our guys

- Priorities

- We are looking for developers that know other code... and it only takes 10-20 hours to get them up to speed vs months and months or years and years. We can't train from the ground up.

- Behind the funding game... robbing peter to pay paul

- Making those hard decisions... who is critical?

- Take care of the assets that help the ship keep running

- Budgetting and setting priorities - working within those budgets - what about your family? Looking for the best bang for the buck

- High level decisions and then trickle down to what is needed

- We get enough smaller jobs... the little things start to sink the ship

- Steve's idea... work on what is being asked for and help make it look better while we are in there - bring the designers back inside to help with the current projects

- Constant process of refinement... less clicks, looks better, more automation, looking for the easy button

- Where are things headed... as a question?

- Things keep changing... because we are in a system, you get cause and effect

- If we don't redo or rework some of the pieces... this ship will sink

- We need take care of the customers but we also need to say no at times.

- We build and build and build - we may need new architecture - things have changed over the course and we need to build and/or adapt - we are not what we started out to be and/or were developed to be

- Analogy - cleaning the house... move everything out and do a deep clean or just clean one area at a time

- What is the vision of where we are going... ok, once we know, let's start moving towards that new model - how do you help spread that vision and direction?

- Breaking and pulling out the logic into their own functions (api sockets, function, objects, etc.) - the key is to isolate logic from the view of the page

- Following the processes and procedures to get to the end goal

- Where is the puck going to be... dream it up, and then trim it down if needed

- Improving from where we are at - ok, where are we going... we need to have a master vision

- By small and simple things, great things are brought to pass - little drops in a bucket, over time, they will add up

- Thinking and considering the choice of languages along the way

- Slow and steady wins the race