Skip to content

Instantly share code, notes, and snippets.

View blademirage's full-sized avatar

blademirage

View GitHub Profile
@blademirage
blademirage / TechChallengeReview_34_20181108.md
Last active November 15, 2018 03:24
Tech Challenge Review Result - 34 (20181108)

Considered this submission as a FAILED case.

  • Submitted solution has a docker environment, all containers can be started normally by start.sh.
  • However when curl-ing to the endpoints from both docker host and container, no response nor error message has been returned.
  • Test cases could not be executed by following the instructions specified in the readme.md.
  • Emailed to candidate to request further configurations and test details, however the reply is just ask us to check our docker/docker-compose version and the same command in the readme.md to run the test.
  • Tested again with the same failed result after receiving the email reply.

Submitted tech challenge:

@blademirage
blademirage / TechChallengeReview_38_20181114.md
Last active November 15, 2018 03:23
Tech Challenge Review - 38 (2018-11-14)

Considered this submission as a PASS case.

Submitted tech challenge:

Pros:

  • Detailed and correct documentations.
  • API endpoints naming follows problem statement.
  • Clean and tidy code.
  • Docker containers are running fine.
@blademirage
blademirage / TechChallengeReview_49_20190116.md
Last active January 16, 2019 04:30
Tech Challenge Review Result - 49 (20190116.md)

Considered this submission as a FAILED case.

  • The start.sh failed to start with errors.
  • Started the docker containers alone successfully by following the instruction, but create and list returns error SQLSTATE[42S02]: Base table or view not found: 1146 Table 'laravel_docker.orders' doesn't exist ...

Submitted tech challenge:

Pros:

  • Clean and tidy code.
@blademirage
blademirage / TechChallengeReview_52_20190208.md
Created February 8, 2019 04:19
Tech Challenge Review 52 (2019-02-08)

Considered this submission as a PASS case.

Submitted tech challenge:

Pros:

  • API endpoints naming follows problem statement.
  • Clean and tidy code.
  • Demonstrated well use of existing frameworks/libraries.
@blademirage
blademirage / TechChallengeReview_79_20190709.md
Last active July 10, 2019 10:22
Tech Challenge Review - 79 (2019-07-09)
@blademirage
blademirage / TechChallengeReview_99_20190910.md
Created September 10, 2019 11:18
Tech Challenge Review - 99 (2019-09-10)