wewert · May 5, 2017 16:58
diff --git a/gistfile1.txt b/gistfile1.txt
 Lunch with Darryl went really well. He was super open with his experience prior to getting the position as a manual QA'er. He talked about working for his company for the last three years and that he was still learning a lot everyday, that he had a mentor there who works with him on expanding his skill set. He explained that there are two roles as a QA'er and how the latter is where the future is heading. There are Manual QA'ers and Automated QA'ers. He first got into QAing as a Manual QA'ers and after three years he has developed enough skills and experience to become a Automated QA'er. The difference mainly is the software one uses to do the work. Darryl specifically told me to study up on Manual and Automated QA positions, Ruby, Xpath, Rally(CA Technologies), Jenkins, CI Pipeline, Cucumber, Capybara, and Celinum. He stated that knowing these softwares will help in the interviewing process.

 My take aways from the meeting was that I was not "lost" like I thought. That I know and am comfortable with how all that software works. It's not much of difference from what I have been learning here at Turing. And that QA is totally different than what I thought it was going to be. Being a QA'er is actually being a developer. I would work with code and write code that test the software. That is really exciting to me because of the path it would lead in a career in tech development.

 My follow ups are to remind Daryyl about the opportunity to shadow him for a day. Two folds of that would be that I can see what his day to day would look like and that his team would get to know me.
	Lunch with Darryl went really well. He was super open with his experience prior to getting the position as a manual QA'er. He talked about working for his company for the last three years and that he was still learning a lot everyday, that he had a mentor there who works with him on expanding his skill set. He explained that there are two roles as a QA'er and how the latter is where the future is heading. There are Manual QA'ers and Automated QA'ers. He first got into QAing as a Manual QA'ers and after three years he has developed enough skills and experience to become a Automated QA'er. The difference mainly is the software one uses to do the work. Darryl specifically told me to study up on Manual and Automated QA positions, Ruby, Xpath, Rally(CA Technologies), Jenkins, CI Pipeline, Cucumber, Capybara, and Celinum. He stated that knowing these softwares will help in the interviewing process.

	My take aways from the meeting was that I was not "lost" like I thought. That I know and am comfortable with how all that software works. It's not much of difference from what I have been learning here at Turing. And that QA is totally different than what I thought it was going to be. Being a QA'er is actually being a developer. I would work with code and write code that test the software. That is really exciting to me because of the path it would lead in a career in tech development.

	My follow ups are to remind Daryyl about the opportunity to shadow him for a day. Two folds of that would be that I can see what his day to day would look like and that his team would get to know me.