We have an Extracts, Transform, and Loads (ETL) team on our project. They take care of a lot of backend stuff. Basically if our system communicates with some other systems, this team handles the communication. The subject matter expert from this team left the company this year. He was looking for some stability. Good for him.
Last week the team lead of the ETL Team left the company. He had been planning this for about 6 months. There are still some developers left on the team. But they are of the variety that need a lot of direction. I came to this understanding recently when interacting with one of them.
The customer acceptance team found what seemed to be a bug in the system. I got volunteered to do some leg work on the issue. I had the tester run some queries. Then I tested the app in a development environment. Finally I came to the conclusion that the loads were not populating a required database table. Then I referred the problem to the ETL Team.
I got a call from one of the ETL guys. He asked if I had any ideas on how to proceed. What? I walked him through my findings, which I had provided him along the way. Then I gave him some ideas. He started on them. But he got confused and asked if I could help interpret some of the results. Oh oh. I feel a trap coming on.
Making the Master - Sometimes you cannot get access to key blanks. That's okay. You can buy a bunch of locks and study similar keys that work. Or you can go the route of a sm...