P. (206)300-5822
E. [email protected]
L. https://www.linkedin.com/in/dannyatthepark
G. https://github.com/pwrmvspark

Software engineer with previous experience in non-profit healthcare, military, and IT operations. Proven to be empathetic and curious, I am relentless with building relationships and working on innovative projects.

Picking the right architecture = Picking the right battles + Managing trade-offs

1. Clarify and agree on the scope of the system

• User cases (description of sequences of events that, taken together, lead to a system doing something useful)
  • Who is going to use it?
  • How are they going to use it?

• Explain what Docker is
• Explain why Docker is useful
• Build an image with the docker CLI
• Build an image with a Dockerfile
• Use docker-compose to build and run multiple containers

• Install mongodb
• Explain the differences between a database, a collection, and a record
• Add records to a collection
• Get all records in a collection
• Get one record from a collection
• Delete one record from a collection
• Update one record in a collection

• Explain what relational databases are
• Descibe what a schema is
• Describe what a query is
• Use MySQL to create schemas
• Use MySQL to run queries
• Build and run join queries in MySQL

Below are many examples of function hoisting behavior in JavaScript. Ones marked as works successfuly print 'hi!' without errors.

To play around with these examples (recommended) clone them with git and execute them with e.g. node a.js

(I may be using incorrect terms below, please forgive me)

• Describe the concept of resources in relation to REST and APIs
• Identify RESTful conventions for API routes
• Explain what express is and why it's useful
• Build RESTful routes using express

• Describe the process of solving a problem
• Solve a problem using a specific problem solving technique

Turn to your neighbor and describe a problem solving process that you've used in the past