Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I like the re-design, I really do, but it's hard to be impressed when the same lessons that were broken a year ago are still broken and impossible to finish.


I went through their Python tutorial about a year ago and kept running into problems with the Save and Submit button not doing its job. It would just hang until I reloaded the page (sometimes losing my work if I didn't/couldn't copy the code I'd written.) I didn't try to find out the cause of the problem, granted, but it made me want to not try any other tutorials.


we've fixed a lot of the issues - would love for you to give it a shot again and let me know if there's anything i can do to make your experience better!


I'll check it out again, thanks :)


Can you elaborate? I am a user, and I don't understand what you mean by that.


which are you finding errors in? we keep a pretty vigilant watch on broken exercises (there's a dashboard in our office and we respond to bug reports as well) -- would love to fix these ASAP. thanks!


I just tried the CSS Buttons course on a lark, because I felt I'd be able to breeze through it. I may have hit "Reset Code" at some point, because around checkpoint 4 or 5, the CSS was wiped out and the HTML was back to square one.

I quickly retyped everything, but... only the HTML changes seemed to take effect. I tried targeting the CSS to a class I put on the HTML, then to an id, then to the div itself, and a bunch of different simple litmus tests for whether or not it was working like just applying a color, but nothing worked.

After each change, the preview pane would re-render, so it was picking up the changes. I tried viewing the preview in full screen and refreshing, but nothing got the CSS to apply again.

Anyway, the site looks great. Congratulations on the revamp regardless of nitpicky bugs.


I did the CSS Buttons project earlier this week and had the same issue you described. After checking the Q&A Forum, I realized I needed to include the stylesheet. That fixed the issue. I don't think this is a bug with that project.


Apigee API (2/21) and WebShell API (5/7) are throwing random errors. By the way, I have reported these 2 times before and no one had replied or even acknowledged my reports.


apigee and webshell courses are created and maintained by those companies (our platform lets anyone create courses), so it's unfortunately up to them to edit -- we'll ping them regardless.


Maybe adding a disclaimer to the API section would help then. those were fairly prominently displayed when I first started them and I couldn't finish either of them.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: