Is there a coding standard that beginners should follow for their projects?
Can I simply "YOLO" as long as my project functions? My concern is that I'm not following industry standards, which might affect my future internship interviews if they look into my code and inquire about it, and I'll be clueless.
Also, when collaborating as a team in a hackathon, how can others easily understand and follow my code if my code is not following industry standards?
How do we decide what languages, libraries, and frameworks to combine in order for our project to work?
Is this something we decide in the beginning prior to coding the project (Personal and working on a hackathon project with others)?
Is one of the hard parts of programming figuring out other people's code and building upon existing codebases created by others?
Outside of writing clean code, does it matter which function or tasks I tackle first in my project, or does the order of stuff in the code base does not matter?
My apologies if my question was difficult to understand. What I meant to ask is, is there a recommended structure for writing codes in programming? #technology #dev #programming source