- Be able to delete all your code without feeling sad about it. It's freeing to be able to delete code if a better solution presents itself. Generally these things can be found out by talking to business people and other developers, by having a session where you draw the proposed solution out on a piece of paper or by just iterating through it yourself.
- Confidence comes from trying, and failing, and trying again.
- Burnout is real. Know when you are close to it by knowing what triggers your anxiety and stop. Having the ability to remove yourself from a stressful situation, even if just for an hour makes all the difference .
- Test your steps. If you can write code to test your steps then it's great but most of the time a simple browser reload/button click or command line run action with verify if your change works will be good enough.
- It's fine if you don't know. Having the ability to ask for help will mostly be met with respect.
- You are not defined by your code as a person :)
- Theoretical pureness mostly gets in the way of solving an actual problem because of the endless debate it sparks in a team. If your goal is to write code that is readable for someone in the future then it doesn't matter what design pattern you use. Computers are fantastic at understanding code. Humans however need some help.
- Try and clean up as you go. Like your home, if the dishes pile up too much it becomes unliveable.
- Lastly, learn how to understand legacy code. It's a fantastic snapshot into the way the business was thinking at the time and to see it evolve and be that change is a privilege to be part off.
- Confidence comes from trying, and failing, and trying again.
- Burnout is real. Know when you are close to it by knowing what triggers your anxiety and stop. Having the ability to remove yourself from a stressful situation, even if just for an hour makes all the difference .
- Test your steps. If you can write code to test your steps then it's great but most of the time a simple browser reload/button click or command line run action with verify if your change works will be good enough.
- It's fine if you don't know. Having the ability to ask for help will mostly be met with respect.
- You are not defined by your code as a person :)
- Theoretical pureness mostly gets in the way of solving an actual problem because of the endless debate it sparks in a team. If your goal is to write code that is readable for someone in the future then it doesn't matter what design pattern you use. Computers are fantastic at understanding code. Humans however need some help.
- Try and clean up as you go. Like your home, if the dishes pile up too much it becomes unliveable.
- Lastly, learn how to understand legacy code. It's a fantastic snapshot into the way the business was thinking at the time and to see it evolve and be that change is a privilege to be part off.