Tips and advice for developers
1. Level Doesn’t Matter, Results Do
If you are solving people’s problems, no one asks how long you have been developing. If a subject interests you, don’t let its name deter you from learning more about it. It might be useful sooner rather than later because you never know what you’ll be asked to build.
2. Don’t Memorize
Discover how to find the information you need. I’m not talking about Stack Overflow or GenAI. Know where the specifications or documentation for the tools and languages you’re using are stored. Discover who writes the best guides.
When using a JavaScript conditional operator, it doesn’t matter if you can’t remember which comes first (? or:). It is critical that you understand when to use a conditional operator and where to find the exact syntax.
Tools change all the time. Verify the document version you are reading at all times. Whether it’s a newsletter or that one friend who is really interested in CSS, find a way to stay current.
3. Go Deep on the Basics
As someone who has worked with three different JavaScript frameworks in three years, I can tell you that learning a new tool in the ecosystem is much simpler if you understand the fundamentals. You’ll most likely write software that is more reliable and easier to use. Because you were unaware that features already existed, you won’t attempt to write them. You’ll be able to predict mistakes before you make them and comprehend the mistakes you make better.
4. Systems Thinking Will Get You Far
Any bug must be troubleshooted using systems thinking. In the event that the toaster fails to turn on, you won’t think to check the plug in the wall. It is simpler to anticipate edge cases and create new features when one can view the system as a whole. To learn more about developing mental models for your codebase, see How to Begin in a New Codebase
5. Trying Before Asking Ensures It’ll Never Be a Stupid Question
Typically, developers are focused on solving problems. They’ll likely want to look into why the apparent fixes didn’t work if you can demonstrate that you tried a few different approaches and they didn’t work.
6. Every Line of Code is a Liability
Write code as though it needs to be fixed by someone else. (Even if, in six months, that someone is just you.) Install packages as though you will need to update them often. To avoid later breaking something by accident, note the reason. Before integrating an opinionated tool into your system, find out how its views conflict with the features you require.
7. Practice Reading Others’ Code
You might think that you will frequently get to create brand-new apps because of the way software development is taught. Fixing and adding features to an existing codebase is far more likely to be your task. It’s possible that you read code more often than you write it. Develop your ability to read code and refactor it without adding new errors.
8. Test, Test, and Test Again
According to Chocho’s remarks at DevNexus 2024, “Software is practice. Code is theory.” Always test and run your code before submitting it for review. Try to write as many tests as you can. You will become a better developer by foreseeing how a user might break your code and considering options beyond the happy path.
9. Practice Turning Requirements into Software
Ticket #387
- Add a button to the page that opens a modal and allows a user to edit this data.
It is expected that you can convert a requirement like that into a set of steps or pseudocode. If the ticket is too vague, it will be your responsibility to get the answers you require.
After you’ve ironed out those steps, you’ll be expected to convert them into code and (hopefully) test it. Then it will be your responsibility to get that code through your company’s version control, review, QA, and deployment processes.
Open Source is a great place to practice this.
10. Community is Extremely Important
Social media posts won’t give you the most objective, nuanced viewpoint. You need a network of people you can turn to when you need that viewpoint.
This includes mentoring. Attending regional conferences and meetups is a terrific way to broaden your perspective on development and develop your network. You can gain insight into the viewpoints of senior developers by joining networking groups.
Don’t attempt to complete this task alone. With so much information available, it’s simple to become overwhelmed or develop tunnel vision.
11. Find What You Enjoy About Programming
I’m not saying become the elusive Passionate Programmer or love your work. But learning new things all the time exposes you to recurring discomfort. You will burn out if you don’t know why you want to wake up and continue doing that to yourself. You need to understand why you are doing it, even if it is selfish.
12. Everyone’s on Their Own Journey
The careers and content of others are not in competition with yours. Your path to success might not be the same as someone else’s. Pay attention to your strengths and distinct viewpoint. Discover your voice and speak it. It’s something that someone wants to hear.
Conclusion
You might assume from looking at my (or anyone else’s) profiles that I had an easy time getting to the position of mid-level developer. The opposite could not be more true. I’ve cried and stumbled, broken prods, burned out, and fallen down a lot of rabbit holes.
I must therefore sincerely thank my family, friends, and the tech community for keeping me afloat. I also want to thank a lot of my coworkers for believing in my abilities. I couldn’t have progressed this far without you all. I am so appreciative that I have.
As a Newbie, I am continuously searching online for articles that can help me. Thank you