Sean and I going over the adilas label builder. He was requesting a smaller grid layout, options to zoom in on the smaller labels, and better save options. He had lost some work because he wasn't pressing save enough. Maybe automate that. Anyways, we pulled up some code and were looking around for the variables to control the grid layout and grid sizes. We tweaked some things out and pushed up the new code. He was working behind the scenes to make sure that everything was working. Small little microburst on the label builder.

Small work session between John and I. We started out by pulling up a local code branch and doing a visual review of the changes. We were working on the add/edit location page. We then moved into talking about making plans (frontend, backend, and overarching architecture stuff) and carving out timeslots for finalizing those plans. We planned 2 days a week for 2 hours a piece, all through the month of June. Putting some placeholders into the mix.

Another topic of conversation was about IP (intellectual property) and gathering things up. This includes raw code, raw graphics, and other assets and resources. Currently, I have a bunch of this stuff on my local computer but nobody else can get to it and it's not super organized. Anyways, that will be a future project as we move forward.

I promised John that I would check on what it would take to be able to gift a percentage of ownership for some of the bigger framework projects that we have coming up. I'd like to help incentivize our guys/gals to help us work on those pieces.

We talked about themes (existing and possible themes) as well as coming up with our own themes and custom CSS (cascading style sheets and full application layouts). Along those lines, we also need to plan in progression and deprecation of those visual assets and themes. Our product needs to keep changing in order to keep up.

John really loves feedback, and he was asking if we could, on purpose, include some others on our feedback models, internal needs, external needs, and wants of our users and our clients. All of that would be some great information and great feedback. We don't mind changing things, we just need a plan in order to know where we are headed and what the priorities are at this point.

This is more for me, but I was listening to an audiobook - Dale Carnegie - "How to Win Friends and Influence People", and it was talking about avoiding the acute angels or tight spots (with people, projects, and such). You want to keep your options open (like an obtuse angel) vs creating a squeeze or super tight spot (acute angles). Not that you never get into those spots, but you don't try to force anybody into those tight spots. As John and I were talking, that thought came back to me about trying to avoid the acute (tight) angles or tight spots. I'd like to build so that there is room to turn, maneuver, and adjust as needed. Once again, this is more for me than for anyone else.

Emails, light tech support, and recording notes from the past few days. Also, on the phone with a client going over things. Recorded notes for 5/22/23, part of 5/23/23, and all of 5/24/23.