Eric, Steve, and I were on the morning meeting. Eric needed some code signed off. He also had some other questions. Steve was working on his own projects and I was working on my stuff. Lots of emails and what not. After awhile, Steve and I were chatting about progress and where things were headed. We talked about how certain companies really want some hand holding to help them make the jump and transition. We talked about some our efforts in that area.

As a funny side note, we were talking about how some people go through phases. The analogy of learning to snowboard was brought up. The first couple of days and first couple of times can be brutal. We talked getting people through the "this sucks" phase and how to help them keep stepping up. In snowboarding, if they get through the this sucks phase, they end up at the "this is pretty cool" phase. Then real progression can build from there. Sometimes software or software as a service (SaaS) is similar. There seems to be different phases that people need to go through in order to really catch on and buy in or see the possibilities and the vision.

Josh joined the meeting around 10 am. He is working on some consolidated big data reports for a client. This is a multiple corporation report with two years of rolling sales data on a single report. The report has show/hide and slide out type drawers with the data grouped per corporation per month per category. As Josh was showing Steve and I the report... we kept thinking about getting away from transactional data and getting more into data warehousing and aggregated data (pre summed up data per day, per location, per category). That would really help speed things up.

We looked at some other ways of speeding up the reports and even spent some time talking about master corporations and how a master corporation (world) could actually hold the consolidated data on a per location, per day, per category level. There might be some cool options there.

After that, Josh and I spent a good hour debugging one of the reports. We weren't getting very good error messages, so we had to keep moving a break point from top to bottom until we found the errors. Sometimes the debugging process is short and sweet and sometimes it takes hours to get to the bottom of the problem.