3 ms·

I'm definitely sensitive to the unpaid labor thing, but idk how many hours I have spent working on cover letters and my resume anyway, trying desperately to get

I'm definitely sensitive to the unpaid labor thing, but idk how many hours I have spent working on cover letters and my resume anyway, trying desperately to get noticed, only to have no response at all, or just get filtered out in the first step. I have talked to maybe 4 humans total in my couple of years of trying to get a coding job! This makes me excited more than anything, to have something right out of the gate to test my skills on, to be slightly more assured that my work will actually be looked at before I get filtered out... That is absolutely enticing and huge to me, but I get that I am maybe more desperate than most.

djbusby 4y ago
Even after the 10h on code or cover letter there is no assurance your submission will be viewed by human. It's easier to filter out code submission than CV/CL. IME the code-first process is even less odds of humans
zasdffaa 4y ago
Do a good project, put it on a public repo. Point them at it. That will help. Or OS contribs perhaps. Good luck!
- beepbooptheory 4y ago
  Haha thank you, I knew I was doing something wrong!
  - zasdffaa 4y ago
    You're being sarky? Maybe it's too obvious advice, especially my emphasis on a 'good' project but I've seen some pretty pathetic ones inc. someone here who complained no-one was impressed with his work. I looked at his github and it was crap and bulked up with 100s of megs of quite pointless (and uncompressed!) textual test data. Maybe mine's a poor suggestion but I really do wish you the best, it's hard being in that position.
    - beepbooptheory 4y ago
      No no, I apologize, I didn't mean it like that at all. I thought you were being a tad snarky, implying that my efforts haven't succeeded because I haven't made something good yet. But I didn't take it in a bad way at all, we are all trying to make good things, and only sometimes succeeding :). I coded and made things for a long time before I ever even considered getting a job doing it. So, for me it's always a little bit of a struggle trying to find the right "portfolio" project to attempt to spruce up and point to; but I experiment with showing off different things. But that is why the prompted project here is refreshing to me. I don't know if I code better than that person, but I am very careful about what goes into version control. Thank you for your well wishes, one day it will work out for me!
      - zasdffaa 4y ago
        Thank you in turn, I hope you find something soon!
- zasdffaa 4y ago
- veidr 4y ago
  This isn't bad advice, I don't know why you people are downvoting it into oblivion. If there is a coding challenge to advance in pursuit of an open position, and it is not paid, and it will take a significant amount of time (e.g. the 10 hours discussed here) then your choices are: 1.) decide yeah, nah, fuck that job and don't do it 2.) do it, but post it to your git[hub | lab | whatever] as open source, and refer them (and possibly, others in the future) to it 3.) whatever else you would do here, it's not as good as the above two ideas

djbusby 4y ago

Even after the 10h on code or cover letter there is no assurance your submission will be viewed by human. It's easier to filter out code submission than CV/CL. IME the code-first process is even less odds of humans

zasdffaa 4y ago

Do a good project, put it on a public repo. Point them at it. That will help. Or OS contribs perhaps. Good luck!

beepbooptheory 4y ago
Haha thank you, I knew I was doing something wrong!
- zasdffaa 4y ago
  You're being sarky? Maybe it's too obvious advice, especially my emphasis on a 'good' project but I've seen some pretty pathetic ones inc. someone here who complained no-one was impressed with his work. I looked at his github and it was crap and bulked up with 100s of megs of quite pointless (and uncompressed!) textual test data. Maybe mine's a poor suggestion but I really do wish you the best, it's hard being in that position.
  - beepbooptheory 4y ago
    No no, I apologize, I didn't mean it like that at all. I thought you were being a tad snarky, implying that my efforts haven't succeeded because I haven't made something good yet. But I didn't take it in a bad way at all, we are all trying to make good things, and only sometimes succeeding :). I coded and made things for a long time before I ever even considered getting a job doing it. So, for me it's always a little bit of a struggle trying to find the right "portfolio" project to attempt to spruce up and point to; but I experiment with showing off different things. But that is why the prompted project here is refreshing to me. I don't know if I code better than that person, but I am very careful about what goes into version control. Thank you for your well wishes, one day it will work out for me!
    - zasdffaa 4y ago
      Thank you in turn, I hope you find something soon!
zasdffaa 4y ago
veidr 4y ago
This isn't bad advice, I don't know why you people are downvoting it into oblivion. If there is a coding challenge to advance in pursuit of an open position, and it is not paid, and it will take a significant amount of time (e.g. the 10 hours discussed here) then your choices are: 1.) decide yeah, nah, fuck that job and don't do it 2.) do it, but post it to your git[hub | lab | whatever] as open source, and refer them (and possibly, others in the future) to it 3.) whatever else you would do here, it's not as good as the above two ideas