Ask HN: Would you hire me (passionate hobbyist programmer) to a dev position?

Post by solomatov » Thu, Feb 12, 2015, 3:42 AM UTC

shayanjm wrote: post #46

No, I wouldn't hire you as-is. Probably not a first-choice intern either. Some notes on why not: + Your web-sume looks rough. As pointed out by others, there are a number of typos (i.e: "and provide an opporunity") not to mention the design itself could use work. If you are GREAT at web design/UX you should spruce it up. Otherwise, kill it and move to a traditional resume. Knowing HTML5/CSS3 today is pretty meaningle…

Post by atmosx » Thu, Feb 12, 2015, 6:23 AM UTC

jorgecastillo wrote: post #83

atmosx wrote: post #78

Earlier quoted context omitted.

I'm impressed by your comments. Could take the time and make a similar assessment of my github[1] account? It's highly unlikely for me to ever work as a developer but I'd like to know what you think of it, nevertheless :-) [1] https://github.com/atmosx ps. In case you take the time to have a look at my repo... Well thanks for your time :-) (everyone else, feel free to drop a line or two about my repo if you like)

>It's highly unlikely for me to ever work as a developer Maybe someday you can work as a developer for yourself. The good thing about a software business is that it's more about business than software. If you can code a working solution to fix some problem that exists everything else is irrelevant. The really hard thing is to identify a problem that's business worthy.

Post by solomatov » Thu, Feb 12, 2015, 7:17 AM UTC

hamburglar wrote: post #94

solomatov wrote: post #91

Earlier quoted context omitted.

>+ Learn how to use git productively in a team environment (this means no more working directly out of master). This is a good resource to that end: http://nvie.com/posts/a-successful-git-branching-model/ But why everybody should use this kind of branching model? Branches have their overhead, namely time spent merging after several days of work.

Saying a person doesn't know how to use git productively based on their personal github projects is simply ridiculous. Nearly everything I put on github is experimental wankery presented as a curiosity, not a release. It has nothing whatsoever to do with my ability to use git productively. I can only conclude that anybody who would make this criticism has a strong "everyone should be just like me" value and is probab…

Post by avinassh » Thu, Feb 12, 2015, 10:54 AM UTC

Justen wrote: post #12

coreymaass wrote: post #2

Since you present your resume in code, I would have to take that into consideration. Your front-end skills are a good start, but I wouldn't hire you based on them alone. I honestly think you're putting yourself at risk but giving a potential employer the code of your resume to judge you by. The outcome is not as pretty as if you just created a standard resume, and I don't know that most people hiring would get that.

Piggy backing off of this, I have an invite to https://careers.stackoverflow.com/ if you'd like to set up your resume there. I set up mine there and it's gotten me a lot of interviews.

Post by gr3yh47 » Fri, Feb 13, 2015, 11:49 AM UTC

hamburglar wrote: post #94

solomatov wrote: post #91

Earlier quoted context omitted.

>+ Learn how to use git productively in a team environment (this means no more working directly out of master). This is a good resource to that end: http://nvie.com/posts/a-successful-git-branching-model/ But why everybody should use this kind of branching model? Branches have their overhead, namely time spent merging after several days of work.

Saying a person doesn't know how to use git productively based on their personal github projects is simply ridiculous. Nearly everything I put on github is experimental wankery presented as a curiosity, not a release. It has nothing whatsoever to do with my ability to use git productively. I can only conclude that anybody who would make this criticism has a strong "everyone should be just like me" value and is probab…