Hey, thought someone else might be interested, here’s a showcase of all my projects: http://selhar-showcase.surge.sh/
And here’s a temporary portfolio i made: http://codepen.io/Selhar/full/pegvmw/
Here’s my github, too, you can see the whole process if you have enough patience to flip through commits: https://github.com/selhar
I’m writing two posts about FCC beta if anyone is interested, i’m not sure when they’re gonna be ready though, I’m trying make my text as direct and brief as possible, otherwise i don’t think people are likely to care too much about it. One of the posts is about some of the pitfalls from FCC and general self-learning tips, and the other is about resources that helped me during FCC beta.
I feel that the font sizes fo the page title and the short description are relatively small; their current font sizes look like they are out-of-place footer content. My attention was immediately drawne away by the projects
Lowe case “I” in the description
The FA icon for FCC currently opens the same page in a new window—is that intended?
Image quality is consistent, it could be an artefact
Icons at the bottom are invisible and only become visible on hover
Comments on some projects I sampled (and haven’t seen before):
The example output string may be too long and there is no word wrapping
An empty string returns an error TypeError: Cannot read property 'join' of null—given the heading that the project is under and that it’s placed right at the top in the personal portfolio page, it may be worthwhile fixing it
You may want to check this for other projects in the same group, too
<audio> has a delay on Safari. As far as I know that delay is impossible to get rid of without using other APIs, such as the Web Audio API
Looking forward to read the posts regarding your journey. Good luck with job hunting.
First of all, congratulations! I think you’re the first person to complete all of these projects. Even though you didn’t formally get all of the tests to pass, from doing a quick spot check, this looks like excellent work!
Did you also work through all the new coding challenges? Such as the Information Security challenges, and the advanced Node challenges?
I know you mentioned waiting until these are live on freecodecamp.com before you get the tests to pass. Well, we’re working on shipping beta as soon as possible.
Could you create a fork of your current repo and focus on getting the tests to pass on all of these? This would be extremely helpful for a number of reasons:
We would like your feedback as to the relative difficulty of each project
as you did them based on your knowledge at the time (perhaps you could rank them on a scale of 1 - 5?)
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.
All of this would be extremely helpful for our curriculum development team.
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.
Sure, i’ll start working on it right now. Where can i give this feedback, here or on github?
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.
Wow, massive props for being (probably?) the first one to finish them all!
Love your “cupcake landing page”, but I have one piece of feedback: it might be a good idea to preload those images at the bottom before they’re needed, otherwise users on slower connections are left waiting for them rather than seeing them as soon as the mouseover is triggered on the corresponding icon.
From the beginning i wanted to finish all projects, since some projects are really short, having everything in one big folder was easier to deal with, rather than creating a new repo for each project. There’s not a lot of logistics around it, at the beginning of each new certificate i made a boilerplate (to use in future projects) and created a new folder whenever i needed it.
Since i worked at one project at a time (instead of bouncing between them), the github aspect of it was easy to deal with, i work on a project and i commit files only to that project, so if i ever need the commit history, i have a clear understanding of what was going where. That’s basically how it worked for me.