100 Days Of Reflection (And Code)

TL;DR: How to enrich the #100DaysOfCode challenge with a "reflection surface" for thoughts and ideas?

Hi there! I've read about the challenge about a year ago. As I've come across a lot of peoples' reviews on the challenge, it seems that mostly newer developers take it up. And it makes sense! In the beginning of learning any craft, actually practicing it is very beneficial to the learning progress.

Now I wonder whether an intermediate developer like me can benefit as much. Practice never hurts, but according to my experience, at some point the challenging parts of developing something are not in finding the correct combination of characters ("the code") that gets the job done. It's about structures on a larger scale and finding the right level of abstraction in implementing, designing, deploying, and of course documenting the solution. And learning/improving in these areas - at least to me - goes hand in hand with talking about them to someone else! Getting feedback and toying around with ideas help me see and examine aspects that I might have missed about the problem, the solution, or the user. Ideally, it spawns new ideas on both of our minds, and we both learn something new. At least for me, 15 minutes of a good discussion can yield as much of a learning effect as a whole day of coding.

So I expect working 100 days on something by myself - with occasional motivational exchanges via social media channels - might be a lot of fun! But I suspect that I won't learn a lot. This is not a bad thing since it'd still be fun, right? I still wonder how to enrich the challenge with some kind of "reflection surface" that I can bounce off thoughts and ideas - ideally with more than 280 characters per message.

Thoughts and Ideas, anyone? :)