Meeting with Cody. Going over UML diagrams that he is working on. Talking about efficiency, reuse, pros and cons of copy and paste, pros and cons of duplicating data, and math on the fly or precalculated math. Lots of good topics. Here are some of my notes:

- The importance of refactoring. Keep refining and paring things down. Make it smoother as we go.

- Talking about mini conversions and other options. Mini conversions is a sub of sub inventory (parent/child inventory). For example: Say you have something that gets sold by the case, by the bottle, and by the fluid ounce. You have to be able to go up and down the conversions to show what is really there. True inventory tracking.

- Talking about lots of suggestions and what makes sense to change out and/or leave.

- On the mini conversions, we might be able to hold the conversion id's and the math all on the same table. Help the users setup the conversion charts and/or relationships. Especially if we don't know the conversion factors or ratios (custom conversions or custom units of measure).

- We have had a lot of wild west style development (anything goes). There is a need for specific roles and company structure (adilas jelly fish model - future plans for where we are heading as a company).

- We mix so many different business verticals. That has been a huge blessing but also a small curse (so diverse).

- Cody was pitching that we need a primary role of a database admin type person (specialists per role). Creating the chain of command, down the different roles. Basically, turning the wild west into a more modern city (modern development environment).

- Talking about someone who knows how to work really hard and how to help them to work smarter and use technology.

- Cody wants us looking into growth, in the long run. Talking about a master plan and then breaking things down into more digestible pieces.

- Talking about internal education and structure. We need our team to know what to do and how it (all of the pieces) fits with the bigger picture or the whole.

- Figuring out what we have, suggestions for what to change, and future plans.

- We then got into time sub inventory and parent/child relationships. It gets deep, pretty quickly.

- Growth is hard to manage sometimes.

- Talking about independent developers, light guidance, and working on our own. Reasons for building out the UML diagram. Not just for Cody but for all other developers who will be working on this project.

- Building out the dream. Getting organized (not really official, but pretending that it was official). It will all help in the long run. Risk vs rewards - push/pull in the organization. Unofficially organize ourselves (at least on the development side).

- Link to the interactive map - small visual for how things are organized.