QuincyLarson: QuincyLarson: Did you also work through all the new coding challenges? Such as the Information Security challenges, and the advanced Node challenges?

I read them but i didn’t do the challenges, i don’t really learn a lot through exercises.

The back-end challenges have excellent sources of information about security, but i felt like the projects didn’t really act upon them. During the API projects you learn about Mongo/mongoose, but only end up using that knowledge on the information security challenges, which ends up making them not really about information security, and more about mongodb CRUD. This was the only thing that seemed off to me, the lack of security (sessions, password management, authentication, etc…) in the security projects. Also, since it’s about learning TDD, it seemed strange to use the freecodecamp test suite, after all i was learning about how to use TDD. Creating the tests from scratch felt more intuitive.

QuincyLarson: QuincyLarson: Could you create a fork of your current repo and focus on getting the tests to pass on all of these?

Sure, i’ll start working on it right now. Where can i give this feedback, here or on github?

QuincyLarson: QuincyLarson: We’d like to know much time it takes you to take your existing projects, which fulfill user stories - and get the test suites passing. If you can keep track of the time it takes to do this on each project, it would be really helpful.

Oh, this is something i kept thinking about while i was doing the curriculum. Every single project takes less than a day to complete (complete the minimum requirements, not necessarily doing the front end/usability work). The bottleneck is always knowledge, for example, whenever i began a new curriculum the first projects could take weeks to complete, but the last 2 or 3 always took a day or two. Even the anonymous imageboard took me roughly a day to do the back end.

And while we’re at it, i have a few questions about these projects, some of them i straight out didn’t understand what the requirements were, like this one, the “relative likes” part seems a bit odd, considering the previous projects were fairly realistic in their approach. This one seems to add a feature that doesn’t really add anything to the curriculum as a whole. I think this was the only project where i felt underwhelmed, like the project wasn’t really worth the time. It’s basically API retrieval with a basic like system (and a relative like system which i couldn’t understand), but the problem is that we already did almost exactly that in the URL shortener project, except that the url shortener is much more realistic and elegant.

The imageboard project is also very strange, it asks for multiple boards, but in reality there is only one board implemented, and the end user will be unable to create multiple boards. So i don’t really get why is it supposed to be a multiple-board imageboard when you’ll only end up with one, created by the programmer.

I’ll start working on making the user stories pass and post it here when i’m finished. Thanks a lot for your work.