Hey everyone. We’re adding a new year-long 12in23 badge for completing all the of the monthly featured exercises in one of their featured languages.
You’ll be able to check your progress on the 12in23 page once Mechanical March starts.
The rules:
An exercise must be published during 2023.
You can complete/publish them at any time during the year not just the featured month.
You need to complete each exercise in at least one languages (it’s not required to complete it in all the featured languages)
You can mix and match languages, so for Feb, do 3 in F# and 2 in Elixir, etc. So if you’d previously completed a Functional February exercise in F# in 2022, but you want to make it count for 2023, solve the same exercise in Elixir or one of the others (note that you can “Disable Learning Mode” - look for the ... button on the track page - if you don’t want to work through the whole syllabus, although we already recommend syllabuses if you have the time! )
Here are the correct language/exercise pairs to earn the badge:
Question: what do we do when one of the featured exercises was published in a previous year (in my case F#/robot-simulator from 2022)? Can we modify the code and re-publish it, or (perhaps better) do just that exercise in another language? Either of those seem reasonable.
I assume I don’t need to write off the F# track entirely and restart in Elixir (or whatever) - the rules don’t say that all exercises that month need to be in the same language, so we can mix them up.
I’m sorry if this is the wrong place to post this, but I just finished and published a solution for Pangram in C++. However it’s not showing up in the #12in23 tracker, while Secret Handshake that I solved earlier in C++ does.
I should also note that I didn’t receive a Mechanical March-badge for solving 5 other exercises this morning.
Thanks for this exciting and fun year long challenge!
If one of these languages doesn’t have a exercise, this should be considered a bug?
Clojure, for example, doesn’t have the Yatch exercise yet. Although I could do it in another language, it would be nice if I could solve all five exercises in one language to take advantage of what I have already learned.
Not a bug, but probably something the maintainers would choose to prioritise. Our tracks are created by volunteers so exercises are added on a “what they feel is most important” basis. (cc @porkostomus who maybe will add it for you )
Yeah it just means that it wasn’t one of the 76 exercises added by the v2 maintainers. It’s one of our canonical exercises (assuming you’re referring to yacht), so if I update the exercise generator we should be able to port it automatically. It just hasn’t been used in years and we’ve since switched templating systems, but I’ll bump this up on my things to do
Small typo at the top of this thread: Mechanical March exercises also include Pangram. This is shown correctly on the 12in23 page, so no great harm done.
It seems wise to roughly plan out all featured exercises for the rest of the year already, so that it can be made sure that fitting exercises are still left for the later months.
If you’d like to start a new thread with some suggestions in and encourage others to partake with suggestions, I’m sure @ErikSchierboom would appreciate that!
)
)
