Live data from Hacker News

Build your portfolio by working on interesting projects

zyring.com

31–40 of 50 posts

Re: Build your portfolio by working on interesting projects

#31
post #5

Earlier quoted context omitted.

Co-founder here. I am completely agreeing with you and I am one of the people who hates the culture you mentioned. We created this website for people who are new to programming or people changing careers. People who have not taken a university path (taken online courses, self taught) but find it difficult to get a job because they don't have anything on their resume. They find it intimidating to contribute to open so…

I am one of those self-taught no degree developers currently building my own portfolio. It definitely is intimidating to contribute to open source projects not to mention learning the projects/technology to be able to contribute. But as for my own projects, it's increasingly discouraging to find out my ideas have been done inside and out. I think the only thing keeping people like me going is the passion of figuring…

I don't think anybody doing your project should discourage you. It's usually in the process of trying to do something that has been done before that you get an insight or think about a better way of doing it. Plus, doing things that have been done before is a very good way to learn. Thats how in the old days apprentices became masters.

As for the alg/ds. In my opinion, there are some fundamental things that you need to know about DS/alg that make you a better developer. What people usually get wrong is assuming that it is the applicability of the algorithms or datastructure that matters ( who cares if you know about a Red/Black Tree ! ) . I think its more about the patterns and the way they allow you to think.

Understanding how tree traversal is done may not be directly useful in your work but helps you understand recursive thinking which is super important. Knowing how QuickSort/MergeSort work doesn't have any application in real life but makes you think about problems with a divide/conquer approach in mind which is again super practical. You will never write a Hash/Dictionary but knowing what is the difference between one and an array has immense applicability on your work.

My advice to you: stay away from memorizing DS/Alg. Throw out your "cracking the coding interview" book if you have one and pick a algorithm and datastructure book and try to understand it. Then you can move on to solving problems yourself and you will realize that you are a better developer for it. Here is what I would suggest:

http://ocw.mit.edu/courses/electrical-engineering-and-comput... http://interactivepython.org/runestone/static/pythonds/index...

Of course, you don't need to know all of the stuff here :)

Re: Build your portfolio by working on interesting projects

#33
At first I thought this is an article with tips to build a portfolio. Then I thought ah, they help me publish my stuff, like dribble or behance. Then I arrived at the node.js setup page and I closed it.

I recently started to update my GitHub profile for the same reason and created my username.github.io page with a simple landing that summarizes my interesting repos. My point is that the need is definitely there, but I think the message of the site is "if you have zero imagination how to show off that you can code, here are some projects for you".

Re: Build your portfolio by working on interesting projects

#34
post #19

Earlier quoted context omitted.

Thanks. There's probably a lesson here: if two paragraphs of text in a comment on HN does a better job of explaining what your web site does than its own landing page does, maybe your landing page needs a bit of a re-think.

lesson learned :)

If there is one thing I find absolutely abundant, it is programming projects that don't pay anything.

Re: Build your portfolio by working on interesting projects

#35

At first I thought this is an article with tips to build a portfolio. Then I thought ah, they help me publish my stuff, like dribble or behance. Then I arrived at the node.js setup page and I closed it. I recently started to update my GitHub profile for the same reason and created my username.github.io page with a simple landing that summarizes my interesting repos. My point is that the need is definitely there, but…

Thats a harsh way to put it but somehow true. Its less about imagination and more about ability.

The people who need this site the most are people who are new to programming or don't have any university background (online courses, self taught). Unlike you these people DO struggle starting their own project and they DO need some help setting up their node.js environment.

The problem is that many of us who learned programming on our own have gone through these initial struggles (although we might have forgotten it). People who are learning online are led to believe that becoming a programmer is as easy as taking a code academy course and when they finish the course, they can't do much cause they have been gamified and handheld too much. Most of these people are giving up because there is this sharp fall from finishing an online course and becoming a 'developer'. We are trying to help these people.

Good developers are not in terrible need of a portfolio but the new ones or the ones who are changing their career path are in need of it to actually get a job.

Re: Build your portfolio by working on interesting projects

#38
post #29
post #26

Work for free and don't get paid, because, hey! You'll get tons of experience and build your portfolio. Now on a crowd-source scale! Sucker!

I'm guessing you are someone who does not enjoy programming? Did your parents pressure you to take it up to have a well paying job?

> I'm guessing you are someone who does not enjoy programming? Did your parents pressure you to take it up to have a well paying job?

I do like programming, and I can at least empathize with the parent's skepticism. I do recall the lessons that my other freelance colleagues have told me about 'work-for-free' schemes in different forms. I don't think that's what is happening here but I can understand why some might feel that way.

Re: Build your portfolio by working on interesting projects

#39
post #35

At first I thought this is an article with tips to build a portfolio. Then I thought ah, they help me publish my stuff, like dribble or behance. Then I arrived at the node.js setup page and I closed it. I recently started to update my GitHub profile for the same reason and created my username.github.io page with a simple landing that summarizes my interesting repos. My point is that the need is definitely there, but…

Thats a harsh way to put it but somehow true. Its less about imagination and more about ability. The people who need this site the most are people who are new to programming or don't have any university background (online courses, self taught). Unlike you these people DO struggle starting their own project and they DO need some help setting up their node.js environment. The problem is that many of us who learned prog…

It feels that you want to solve multiple problems at once, not impossible, but more complicated. There is a great leap between installing git and node.js and writing a working, publishable project. I wish it was that easy. The site also didn't explain the process of creating a project from start to finish. It would be nice to see the time requirement for completing one. Is it 1 day or 1 month?

I definitely agree that there is a great drop-out among wannabees, but for them codeacademy style portals are a better fit imho. I tried to teach my designer girlfriend using codeacademy and it didn't go very well, but it was probably a motivational issue. Then I showed her how to modify HTML and she is able to update her site now without my help. So finding the sweet spot it very hard and I feel you need to target more accurately. For example are you sure somebody just learned about functions, for loops and arrays are OK with command line tools and understand how GIT, Grunt, Gulp and node.js relate?

Post reply on HN