all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||
|
|
|
Yellow
|
|
|
Sorry, no photos available for this element of time.
|
|
|
|
Notes:
|
|
On a GoToMeeting with Steve. We started out the meeting going over some meeting recaps and discussions we have had with other team members. Some fun stuff is going on. - Steve and I talked about how the new way of building stable features in Adilas is by getting multiple facilities to build things to spec and then virtually ship them to the jobsite for assembly and finishing. We used to build everything onsite with one or two developers. Now we are trying to coordinate teams and get pieces and products from multiple places like a bigger construction site. Interesting analogy. - On priorities and delegating... we already do some of that by not getting to certain things. When you start delegating, start with the small things that you don't get to. You may not be able to get to them anyways, may as well let someone else take a crack at it. Also, if they do a bad job, you may have to help fix it or guide them on what to do. That is progress. - Some of delegation is letting people do what they like to do. It then becomes easier because they have an internal motivation of sorts. - Working with pallets and visual displays. Think of an artist and how they arrange their colors and tools. An artist's pallet may change day by day if needed. Steve was comparing this to how he wants to be able to setup custom dashboards, customer interfaces, and giving clients and users options to use any tool in the shed and set that display or interface up as they see fit. - Sometimes things need to happen in order for the next action to take place. Often that is easier to see looking backwards but those chains of events are very important and provide the basis for what is really going on and happening. - Eric called but didn't have any wi-fi. I told him I would switch and work on the sub queue project. |