Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

General Discussion

Posted by Jebadeiah Jones
Jebadeiah Jones
10,429 Points

May we get blank workspaces for code challenges?

I find that, while working on code challenges, the errors and returns are less than helpful at times, especially when there's something fundamentally broken with my code. It's very helpful to be able to use a workspace to write and test the code out in and then move that code into the code challenge to see if it fulfills all of the requirements set out by the challenge. Has there been any consideration in adding the option to open a blank workspace directly from the code challenge?

1 Answer

Steven Parker
Steven Parker
231,198 Points
Steven Parker
Steven Parker
231,198 Points

At the top of every page, including challenges (and this one :arrow_heading_up:), there's a menu bar with a "Workspaces" item. From there, one more click (on "New +") will bring up the chooser to create a fresh workspace.

Just be aware that the workspaces don't know anything about the challenge objectives. If you misinterpret the objectives, you can write code that will seem to perform correctly in the workspace, but will still not pass the challenge.

Jebadeiah Jones
Jebadeiah Jones
10,429 Points

Egg on my face, thanks! I can't believe how large that link is and I haven't noticed it. Yeah, I like to use the workspace to troubleshoot things like syntax errors, as the code challenges don't always do a great job at pointing those out. You can usually test the code to an extent, too, by printing your results and seeing if they come out properly.

Anyways, you know all this. Thank you!