In early years the best advice I got was two-fold: write as much code as possible, but avoid “spaghetti code”. Good comments & breaking things into their own class/subclass early on helped in learning more complex aspects such as memory management & persistence layers. Learning to ditch “if” logic, etc. comes later as you refine. Then, CodeSignal launched and I could challenge myself to solve a problem in fifteen different languages: this really showed me where I had to improve and where I was excelling.
Some languages & frameworks that seem attractive on discussion forums will continue to catch your eye long into your career. I like your approach of getting after it, but be choosy about where you’d like to end up on this path- frontend visual work or with the systems they run on.
Languages that I’d say are a benefit to your resume are those applicable to the job.. but JS, Java, Python & SQL are super handy across most of this space.
In early years the best advice I got was two-fold: write as much code as possible, but avoid “spaghetti code”. Good comments & breaking things into their own class/subclass early on helped in learning more complex aspects such as memory management & persistence layers. Learning to ditch “if” logic, etc. comes later as you refine. Then, CodeSignal launched and I could challenge myself to solve a problem in fifteen different languages: this really showed me where I had to improve and where I was excelling.
Some languages & frameworks that seem attractive on discussion forums will continue to catch your eye long into your career. I like your approach of getting after it, but be choosy about where you’d like to end up on this path- frontend visual work or with the systems they run on.
Languages that I’d say are a benefit to your resume are those applicable to the job.. but JS, Java, Python & SQL are super handy across most of this space.
Keep on keepin on. You got this
Thank you so much! 😊