- We were talking about strategies to get projects into smaller pieces.

- Idea - build it backwards - functionality first, maybe even hidden values, then build in the front end (how to supply the functionality).

- The smaller we can break it up, the easier it is to develop and the easier it is to merge back in (merge conflicts).

- We are struggling dealing with transition times (in/out of the project). Also remembering where we were working at and what the flow was when we left that project. Too many things to keep straight.

- Distractions and dealing with that. We are constantly being pulled in every possible direction. It makes it really hard to get good dedicated time and stay focused.

- Projects that Alan is working on - Invoice due date, metrc package stuff, metrc transactional reporting for sales, training developers, code sign-off stuff, and other distractions. Not to mention round 5 of the tax update, discounts on my cart favorite buttons, USAePay reoccurring invoices, USAePay chip reader stuff, permission refactor, corp-wide settings object, breaking up the database into different datasources, all of the sub inventory stuff, plus tons of others. Too many. He is going to focus on the two metrc projects first. Then we'll talk about the next one.

- Alan got assigned to work with a new developer.  Adding on a new guy to help train adds stress with everything else he has going on. I understand. Crazy times.

- Moving to a bigger team approach vs just a single developer. We gain traction as we work together to get things done. By ourselves, we can go really fast, if not distracted and overburdened. We are working on it as we go.