Me: "I've got this repo on Github with millions of downloads and 10k stars. It's at least 20k lines of my own code. Would that be good to demonstrate my coding ability?"
Them: "Haha, no, that'd be too much work for us. Please do the test instead."
Me: "Fine."
Then they rejected me because I used GET instead of POST. Clearly that shows I have no idea how to code.
That was a large (1000+ employee) YC company, by the way.
By the way, thanks for VCCodeVim!
OK, I'm honestly curious here. What was the request, and why did you make such a decision? Do you think it is the right approach in this case, or that it's an insignificant mistake that does not represent a person's understanding of HTTP protocol?
I remember hearing about at least one story where using GET instead of POST lead to disastrous consequences, as some robot crawled all over the "delete" links - but I have to admit, I can't imagine how it would happen without other significant design flaws happening as well (as "delete" links being public or robot being able to crawl under authenticated user's identity). This sounds like an error that can cause irrational irritation by the reviewer, but I can't imagine it being the sole reason to decide that the author can't code.
But, IMO, even if you don't know, it's the kind of thing you learn once in code review and then don't worry about again.
Just using POST for everything is a pattern I've seen becoming more popular recently.
IMHO, GET (as of today) gas the issue that it does not support a body. If I‘m executing a search (an idempodent action), how can I nicely pass a JSON object configuring the search? I‘ll just use POST for that... So then we‘re at the point where the url does not work anymore because we have a POST /findEmployee; POST /findContract; ... instead of GET /employee and GET /contract.
Maybe I‘m wrong here, but it doesn‘t like nice in my eyes using POST in that way.
What's funny is that it's literally their job. They receive money for doing it.
Doing a take home is not paid. I have no idea why these recruiters assume it's ok to ask candidates for multi hours work without any kind of compensation.
Also- thanks for VScode vim! I use it and love it. I've always wanted to reach out cause there's lots of features I wish would get implemented. Though even without those it's one of the better vim emulations I've tried, and I've tried many!