Make your code as simple and brainless as possible.
The vast majority of time spent working with code will be debugging or reading other people's code, so if you write something incredibly clever, you're just making the next person's job (who could be you in 6 months) harder.
To add to this is it's harder to read code than it is to write so write simple code so that when you come back to it you can understand.
Remember that, "other people's code" includes the stuff you wrote 6 months ago.
Look at mister 'I remember my code for up to 6 months' here.
Don't take too long trying to figure out a challenge by yourself. Ask questions. Unlike in school, you are allowed to ask for help with your work.
Learn how to write unit testable code as soon as possible (SOLID principles). Learn how to write concise and relevant unit tests. If it's not in your team's culture to write unit tests, then you go be that guy. It's good for you and it's good for the product. Unit tests are one of the few things in the programming community that everybody believes are a good thing.
I couldn't agree more!
I had a great colleague at my previous job, who was great at reminding folks that we're there to get things done together and struggling in silence was the opposite of that. If you can't figure it out after an hour, give someone (anyone!) a holler and get a second opinion.
I think unit tests are something I struggle with a lot due to not having the habit to write them down. Thank you though! The SOLID principles haven't stumbled upon them in my undergrad lol well time to hit the books again on unit testing xD
A community for discussion amongst professional software developers.
Posts should be relevant to those well into their careers.
For those looking to break into the industry, are hustling for their first job, or have just started their career and are looking for advice, check out: