This issue is a discussion for contributors to collaborate in getting ready to be featured in 48in24. Please refer to this forum topic for more info.
We will be featuring Pascal’s Triangle from Aug 27 onwards.
Staff jobs
These are things for Erik/Jeremy to do:
☐ Check/update exercise in Problem Specifications
☐ Create + schedule video
Community jobs
For each track:
Implement Pascal’s Triangle
Add approaches (and an approaches introduction!) for each idiomatic or interesting/educational approach.
Add video walkthroughs (record yourself solving and digging deeper into the exercise).
Highlight up to 16 different featured exercises (coming soon)
Existing Approaches
You can use these as the basis for approaches on your own tracks. Feel free to copy/paste/reuse/rewrite/etc as you see fit! Maybe ask ChatGPT to translate to your programming language.
@BNAndras Thanks for the head’s up! I was in there this morning re-ordering the Track Docs (thanks @glennj for bringing up and getting that issue fixed!), so I went ahead and fixed it:
@ErikSchierboom – FYI, the Python track has forced a recursive implementation here (not that you need to feature a Python solution). Might or might not be worth a mention that different tracks have different implementations/requirements.
A cursory Github search shows CoffeeScript, D, Gleam, J, jq, Powershell, SML, Vlang, and Wren have “Pascals Triangle” as well.
Edit - I submitted PRs for CoffeeScript and D, but if anybody wants to deal with the others, go ahead. Otherwise, I’ll get to it by the end of the week.