You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 1, 2026. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+33-19Lines changed: 33 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,23 +8,20 @@ This repo’s layout isn’t idiomatic to any one language — it’s a mix of E
8
8
9
9
When I first started these challenges, I was in a teaching job and I was completing them between classes and during times when my students had been tasked and was literally doing nothing. These challenges go all the way up to week 4/5. These are not my best work, I was more interested in making stuff work. However, when I quit the teaching job and was able to sit down and focus on quality, I started everything again. I went over the week one python work and moved everything to a standard that any colleage, customer or employer would be more than happy with.
10
10
11
-
So below is a table of challenges that I consider to be complete, and to have been completed to a high professional standard that you'd expect from any work I was doing. Inline docs, testing, linting, static code analysis, CI/ CD etc.
11
+
So below is a table of challenges that I consider to be complete, and to have been completed to a high professional standard that you'd expect from any work I was doing. Inline docs, testing, linting, static code analysis, CI/ CD etc. Each PR for each challenge is listed below. If it's not in this table and it's in the repo, consider it a working draft of my thoughts.
12
12
13
13
14
-
📝 == links to source code / doc tests
15
-
16
-
🧪 == links to test files
17
-
14
+
### Week 1
18
15
19
16
||| Python | Elixir | TypeScript | Go |
20
17
|-|- |- |- |- |- |
21
18
| W1/1| Plus Minus |[][11py]|[][11ex]| ➖ | ✅ |
22
-
| W1/2| Mini Max Sum |[][12py]|[][11ex]| ➖ | ✅ |
23
-
| W1/3| Time Conversion |[][13py]|[][11ex]| ✅ | ➖ |
24
-
| W1/4| Breaking Records |[][14py]|[][11ex]| ➖ | ➖ |
25
-
| W1/5| Camel Case |[][15py]|[][11ex]| ➖ | ➖ |
26
-
| W1/6| Divisible Sum Pairs |[][16py]|[][11ex]| ➖ | ➖ |
Spot something I could improve? Open an issue and point it out — that would be swell.
@@ -51,7 +65,7 @@ The HackerRank 90-day course was designed as a three-month prep for recruitment
51
65
52
66
What I’m noticing, though, is that it’s also improving my authoring skills more broadly.
53
67
54
-
I started in January. At first, I just wanted to get through it in Python — a collection of scripts to store solutions. Then I added per-file unit testing. Then I started doing the challenges in different languages, and it evolved from there. Now it’s basically a code dojo for me, where I’m working through
68
+
I started in January. At first, I just wanted to get through it in Python — a collection of scripts to store solutions. Then I added per-file unit testing. Then I started doing the challenges in different languages, and it evolved from there. Now it’s basically a code dojo for me, where I’m working through each challenge in each language. I'm learning a lot. Especially about parsing text files (_test cases_).
55
69
56
70
I’ll be very pleased if I complete these challenges by the end of 2025 in four languages: Python, Elixir, Go, and TypeScript. The aim is to get a nice 25% language distribution across the repository and to demonstrate competence in basic project layout, standard libraries, testing methodologies, and — most importantly — low-complexity solutions.
0 commit comments