The key to be a wagecuck isn't that difficult, or at least, easier than you think. I'm autistic and also have ADHD, so if I as a sperg can do it, so can you.
None of the bootcamp bullshit, leetcode, 24/7 grinding or scripted speeches; I never prepare for interviews or code in my free time, I, infact, failed multiple techanical interviews.
I take a more unusual approach.
I was hired in 2022, laid off in 2023, and got a new job in 2024.
The key is to send as many applications as possible, and to accept low pay and long transportation hours.
Eventually you will get some interviews.
On the interview, show three of these things:
Analogue thinking - by showing how a gun reloading in video game is similar to device that guards use to count people, you show that you can speak a human language and that your thinking is transferable.
Architectural mindset - by showing how pinging the DB every new page makes much better impact than how a foreach loop is better than Java streams, you can show that you know high level stuff and system design.
Willingness to deal with team BS - no, you won't be the main character. When they ask you how will you deal with conflicts in views/standards, say that you will talk to him, and tell him to introduce some quirks and the standards of the company for you.
I was laughed at by interviewers and didn't even cared; just let them, be glad you wasted THEIR time!!
When I was new, I asked my senior "is it better to use forloop or streams?", he said "use whatever, doesn't matter". That was an eye opener; the micro stuff doesn't matter that much compared to the macro stuff, assuming it's not too bad or messy.
None of the bootcamp bullshit, leetcode, 24/7 grinding or scripted speeches; I never prepare for interviews or code in my free time, I, infact, failed multiple techanical interviews.
I take a more unusual approach.
I was hired in 2022, laid off in 2023, and got a new job in 2024.
The key is to send as many applications as possible, and to accept low pay and long transportation hours.
Eventually you will get some interviews.
On the interview, show three of these things:
Analogue thinking - by showing how a gun reloading in video game is similar to device that guards use to count people, you show that you can speak a human language and that your thinking is transferable.
Architectural mindset - by showing how pinging the DB every new page makes much better impact than how a foreach loop is better than Java streams, you can show that you know high level stuff and system design.
Willingness to deal with team BS - no, you won't be the main character. When they ask you how will you deal with conflicts in views/standards, say that you will talk to him, and tell him to introduce some quirks and the standards of the company for you.
I was laughed at by interviewers and didn't even cared; just let them, be glad you wasted THEIR time!!
When I was new, I asked my senior "is it better to use forloop or streams?", he said "use whatever, doesn't matter". That was an eye opener; the micro stuff doesn't matter that much compared to the macro stuff, assuming it's not too bad or messy.
Last edited:
