gistfile1.txt

what went wrong on your last project?

  - how did you fix it?

what do you think about feature toggles?

if you practice git-flow what are some of the problems with that or other long running feature branching strategies?
  - merge issues?
  - stale functionality
  - complexity

what would you change or reimplement if you could on your last project, why?
  - what did you find out that you didn't know?

  - if you were your manager and viewing the scope of upcoming work would you still do it? 

  - how would you fight for that feature?

describe some of your architectures:

		•	Designed built, and deployed a multitude application utilizing   
		AWS stack (Including EC2, R53, S3, Dynamo DB, SQS and EMR), 
		focusing on high-availability, fault tolerance, and auto-scaling. 
		Developed backend ran on AWS's Elastic Beanstalk and interfaced with a MySQL on AWS's RDS.

how did you ensure "high-availability, fault tolerance, and auto-scaling."?

can you compare nodejs to spring for code quality, maintanince?

	- do you feel it was more concise
	- did you find one hard to upkeep, refactor, test?
	- how were the tools did you implement more than code for common functionality