My career-related content is now open-source on GitHub.
I received way lots of cool feedback for my article Keep Calm and Just Say No To Coding Ch...
For further actions, you may consider blocking this person and/or reporting abuse
This may sound a bit harsh, but I think there is a bit of a divide here, between self-respecting developers with job experience and a fair amount of useful skills that an employer will struggle to find quick replacement for, and beginners with no or very little job experience outside of doing very generic dev work.
Of course there's a spectrum between these two, and anyone with experience has had to build that experience at some point.
It's easy to say "Just don't take the jobs you don't want", when you have years of experience that employers urgently want and live in an area where most others with those skills are already employed by someone else.
At the same time though, I always find it a little bit annoying when any and all conversations about finding jobs in programming get dragged to the level of "I just completed bootcamp and need money", because that's just not everyone in the field.
At the end of the day, the most important part is always: Know what you want, know how much leverage you have, and act accordingly.
For some people this will mean take what you can, and for others it'll be don't put up with bullshit.
I agree and I'm writing to help narrow down this divide.
ThePrimeagen has a good career and won't put up with a coding challenge like I described if he looks for a new job.
I'm writing for the beginners.
I completely understand and relate to your perspective. Having the ability to say "no" is indeed a valuable privilege, and those who are confident tend to utilize it effectively. However, as a beginner myself, I often lack the confidence to say "no." In my situation, I am striving to be accepted and since I don't have any prior experience, I tend to comply with companies' requirements to the best of my ability (Even though it hasn't worked properly yet).
It took me 10 years to go there.
My hope is that you do this trip in a shorter time period.
Hiring really should be seen as a two way street
Update There is now a reaction to my reaction to his reaction and I think it's pretty cool, both because there are more agreements that would have initially believed, and also because our disagreements are pretty interesting
Prime makes videos and courses on solving coding challenges. Thatβs his bread. Of course he wonβt ever like your opinion π¬
As I recall that's not accurate.
Yep "he will never like your opinion" turned out to be very fast a bad prediction because after his reaction and my reaction to his reaction, he made a reaction to my reaction to his reaction, and it turns out we disagree far less thatn initially thought
stupid argument!
"Project challenge" is maybe a better term to use, albeit not commonly used. Most people who hear "coding challenge" are likely to think short and algorithmic challenges, probably due to their rising popularity and platforms like leetcode. Would definitely recommend making an edit to your original post to clarify! β€οΈ
I added a section
UPDATE: What do I mean here by coding challenge?that points to here already