@here ive awoken from my coma. reading what @Oxyrus and @Jim Medlock said has been exactly what i needed. the lessons and focus that was gained from this experience is what will prove more valuable than any tangible prize.

pouring out everything we had about Chingu is what is going to make the most difference in my opinion. getting all of that data together, organizing our mission, recording sound and video promotional material. those adrenaline fueled savage modes is where a primal focus is borne. without that intensity we would not have anywhere near this complete level of understanding of both Chingu as a community and its future as a training grounds.

on a personal level i received both the rejection from LaunchCode and this “failure” in a 72 hour period. both of these were — what i saw — as pivotal moments in Chingu’s future. but i dont feel hurt or really even fazed by any of this. these to me are what the great leaders and revolutionary business people have always talked about when they said success is not a straight line path.

id rather that path to Chingu’s success be filled with moments like these where we learn and grow together than to coast in with little resistance. we eat these losses for lunch like we ate a literally impossible requirement and “missed it” by 2 minutes.

im working on the article now and as soon as i finish that were going right back to the waffle maker and pumping out those cards to close out the MVP. then its onto autobot integration. these are my goals between today and sunday night. i, and i think i speak for all of us, shine when we aim for the moon.

lets dial back from 40 hour binge-rate to standard feverish pace and have this up, integrated, running, and beta tested before voyage 3 drops. thats 12 days. 5 to finish MVP + autobot porting and upgrade + 7 to beta test and improve in time for the launch.

ill let you know when the article draft is ready (probably later tonight / tomorrow because it turns out _today_ is my last day of work until 12/1)