August coding competition post

DevMatch · Aug 15, 2023 · fad6e33 · fad6e33
1 parent 68964c3
commit fad6e33
Show file tree

Hide file tree

Showing 6 changed files with 60 additions and 0 deletions.
diff --git a/_posts/2023-03-27-create-a-problem.md b/_posts/2023-03-27-create-a-problem.md
@@ -130,3 +130,37 @@ DevMatch can use traditional CI/CD builds to run validators. DevMatch will need
 * Continuously query the state of a given build by ID.
 * Fetch artifacts from a finished build.
 
+# Latest
+
+Clone the DevMatch SDK:
+```bash
+git clone https://github.com/DevMatch/DevMatch-SDK.git
+```
+
+Install the dependencies:
+```bash
+cd DevMatch-SDK\validator && npm i
+```
+
+Create a new repository somehwere, I am going to use the DevMatch internal repo:
+![](2023-07-05-19-03-34.png)
+
+I called this repo `nodejs-hello-world`.
+
+We can modify the readme to add some initial instructions. 
+
+We need to create a validator, or just an integration test that will validate our CLI tool.
+
+In this case, I will use `jest`. I created a `.devmatch` folder where I will keep the test cases "secret".
+
+I installed jest:
+
+```
+npm install --save-dev jest
+```
+
+
+
+# Resources
+
+https://github.com/alexgurr/node-coding-challenges
diff --git a/_posts/2023-07-05-19-03-34.png b/_posts/2023-07-05-19-03-34.png
diff --git a/_posts/2023-08-15-11-39-38.png b/_posts/2023-08-15-11-39-38.png
diff --git a/_posts/2023-08-15-11-43-34.png b/_posts/2023-08-15-11-43-34.png
diff --git a/_posts/2023-08-15-11-45-25.png b/_posts/2023-08-15-11-45-25.png
diff --git a/_posts/2023-08-15-august-coding.md b/_posts/2023-08-15-august-coding.md
@@ -1 +1,27 @@
+---
+layout: post
+title: "Coding competition - August"
+date:   2023-08-15 11:37:00 -0800
+categories: coding
+---
+
+# August Coding Competition
+
+A few months ago, we launched a new event to practice DevMatch problems in a hackathon-style competition. We rebranded these hackathons as coding competitions. During these monthly coding competitions, we select two or more problems from the DevMatch platform and compete against the clock to solve them in 2 hours or less. This week we had the August coding competition, and it was awesome! 
+
+We changed to an eventing time and had people join us straight from their internships to work on these challenges. This was also the first time we tried out the super cool [daedalos](https://dustinbrett.com/) environment to solve challenges in the browser. We also had a brand new spring boot coding challenge.
+
+
+We started the contest at 6:25, and barely halfway through, two contestants completed the two challenges! We had to add more coding challenges in the middle of the contest. This very competitive situation led us to find a problem with the ranking not reflecting the correct results, and it was also not automatically updated as it should. All fixed now!
+
+![Ranking](2023-08-15-11-39-38.png)
+
+Contestants are ranked according to the most problems solved, then by total time descending. The total time is the sum of the time consumed for each problem solved. The time consumed for a solved problem is the time elapsed from when the problem was open to submitting the first accepted run plus 20 penalty minutes for every previously rejected. There is no time consumed for a problem that is not solved.
+
+In the end, contestants shared their solutions with the rest of the group and some of their struggles. This allowed participants to learn from one another by observing how others approach the same problem. We are happy that these competitions offer a platform for developers to solve real-world coding problems, test their skills, and compete with others. 
+
+![](2023-08-15-11-43-34.png)
+![](2023-08-15-11-45-25.png)
+
+See you on the next one!