connect with people whom genuine curiosity is the reason for the conversation not the means for a job because isn't that what coding is: sharing it with those who share the same interest with you and create awesome projects that solve a problem that annoys you to oblivion
rant: I forgot why I started coding in the first place. Now found myself optimizing to get hired. The paradox I think here depicts a nuance into what actually gets you hired vs what is perceived to get you hired. Time and time again I find myself trying to optimize my learning...
a developer, a coder, a disciple of the craft where being good just becomes part of the process not part of the result. and just maybe thats how you actually get hired.
guarantee it either, then whats the best part forward? if neither promises a job at the end of the day then ill just do me and pursue the programming language, the tech stack , the projects that piqued my interest because there is where I truly believe is what makes you . . .
well i fell in love because of the idea that I can bring things to life from a thought and iterate over it as many times as i want not because a job hunt determines my projects and pursuit in this coding space. optimization does not guarantee a job nor my curiosity guarantees it
and that is where my break through happen. if i optimize my coding journey to get hired at the cost of everything and not get hired then why did I code in the first place? what happen to my curiosity, passion, and reason why I fell in love with coding in the first place
after some time in this analysis paralysis mode for 30 days straight , I just had to do a full stop to trying to optimize my developer journey to break through this destructive mindset that ate away at my life, health, ultimately . . . my sanity
binary state being: if I do learn optimally = popular programming language + correct tech stack + checklist on company job board match I will get hired OR the other state that conflicts my inner demons: I cannot peer away from the "required projects" + engage in curiosity ...
this question was pivotal to me because now I am revisiting the beginning of my coding journey and what changed along the way. it was a simple reality I had to confront: the fear and anxiety consumed me as I observed the market to believe and push me into this binary state
the follow up question I had to revisit in my mind to fully flush out my thoughts and feelings around this situation: "why optimize for the job market when the first step after hello world is follow tutorial x and build weather app y to get full stack job z?"
learning... path. The learning path being learn language x in this city to get job y because the stack match has the most surface area + volume of opening position. However, there lies the trap that I myself as a "developer" fall into unless I step back properly.
theres so much ai technology: i tried opencode, pending on codex, perplexity, github copilot, claude code. dont have any strong grasp on uses cases but naturally i leaned into opencode and perplexity: both seems like cool pieces that their respective niches
My perspective just changed completely: stop worrying about "picking" the wrong language to get your first developer job. Stop wasting hours to weeks to months googling what is the best language for this type of developer job instead just pick one of the "top" 5 and go deeeeeeepp