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

Can we kill the Bummer Error forever?

I can't be the only one that feels this way.

The code challenge engine is very poor at giving helpful feedback. I don't understand why it doesn't allow you to properly debug your code without having to copy/paste it into a Workspace. You can get errors that are incredibly generic without providing guidance as to what you did wrong. In some cases, I've ended up resorting to swiping an answer from the forums when I would much rather have worked it out myself - it usually is because my output does not exactly match what the challenge engine expects, but it is difficult to tell because I am not able to see either the expected output nor my own program's output.

I wish the code challenges worked more like checkio.org's, where you can see whatever your program outputs (including print statements for more helpful debugging), plus the expected output.

2 Answers

stjarnan
seal-mask
.a{fill-rule:evenodd;}techdegree seal-36
stjarnan
Front End Web Development Techdegree Graduate 56,488 Points

Hi Louis Joyce,

I think you would do well to send this feedback directly to Treehouse as well. This way we can make sure they receive it. Use this email: help@teamtreehouse.com

I agree with you, it could be much better. And we could help them improve it by giving them the feedback.

Cheers for bringing this up.

Eduardo Valencia
Eduardo Valencia
12,444 Points

I agree. You should be able to figure out the issue by seeing the entire error, and not just be left to guess. I think errors should have a dedicated panel.