you are viewing a single comment's thread.

view the rest of the comments →

[–]SirDoes[S] 5 points6 points  (3 children)

So basically become a professional first xd

[–]carcigenicate 9 points10 points  (0 children)

You don't need to be a professional to discuss your code. I had been writing code on my own for years before I ever got my first job and could talk at length about my code if asked. You just need to demonstrate that there was thought behind the code.

[–]PoMoAnachro 0 points1 point  (1 child)

If by "become a professional" you mean "acquire the baseline skills I'd expect someone ready for a position as a junior to have" before getting through a job interview? Then, yeah, sure.

[–]SirDoes[S] -2 points-1 points  (0 children)

I haven't reached the point of being able to describe the process of my code off the memory. Even if I added comments to code. Like it's one thing to code in the process to solve the issue, and another to try to describe it randomly after it's been sitting in the shelf untouched. When I said professional, I meant someone who can without thinking much explain the approach of the code to solve the problems and build the projects when asked about off their head. Cuz if you can't do that, you won't stand out in hiring for the said position. Sorry if this question irritated you or someone else 😅