News for hackers. Stuff that matters.

allisonhouse

Re:Codecademy redesign on Friday May 04, 2012 @04:47PM (#3930295)
> One thing that remains confusing is that mousing over a course that I think is completed displays "Resume Course".

You're totally right. Thanks for the suggestion! We just changed this to "review course" instead. Hope this makes things clearer.

Re:Codecademy redesign on Friday May 04, 2012 @04:45PM (#3930285)
Courses are still courses! Tracks are just a way to group them, in order, by an overarching theme—a needed change upon the introduction of multiple languages. I hope this clarifies!
Re:Codecademy redesign on Friday May 04, 2012 @12:01PM (#3928984)
I don't think so bro -_-
Re:Codecademy redesign on Friday May 04, 2012 @11:53AM (#3928937)
Sweet. Thanks!
Re:Codecademy redesign on Friday May 04, 2012 @11:45AM (#3928892)
A dozen people? That's awesome. Thanks for the support!
Re:Codecademy redesign on Friday May 04, 2012 @11:41AM (#3928868)
<3. Thanks!

> What's with the color scheme?

Haha. I promise there's just one cohesive color scheme I'm working on adding to the whole site, which is what you see on the track index and track pages. The thematic differences are just a side effect of shipping quickly—the visual side will be coming together soon!

> When it comes to the changes to the menu screens and such, why the friction?

I think I have an answer to this question, but I'd really love to hear more of your thoughts on this as far as what you think is causing friction on Codecademy. If you have a chance, feel free to drop me a line at [email protected]!

Re:Codecademy redesign on Friday May 04, 2012 @11:11AM (#3928719)
Indeed! Just published a little blog post about these changes: http://codecademy.com/blog/8-tracks-gets-a-design-upgrade
Great feedback—thanks a bunch, joeag. I'm so sorry to hear the lessons didn't keep you on board, but we'd love to learn more about your experience and what we can do better if you're willing to chat! We're contact (at) codecademy (dot) com—feel free to drop us a line and one of our co-founders will get back to you.
I'm so sorry to hear that silly bug contributed to your departure! I'm the Lead Designer at Codecademy. We're a lot more stable these days (that printer bug was fixed right away)—if you decide to give us another try, we'd love to hear your feedback about the experience: contact (at) codecademy.com. (Zach, our co-founder, makes sure the whole team internalizes member feedback. :D) Either way, thanks for giving us a shot!