It took me almost 9 years to learn this but let me teach you these in the next 5 minutes.
It completely changed my life as a programmer. 🧵👇
It completely changed my life as a programmer. 🧵👇
1. Ask Questions
- No matter how dumb you sound
- No matter how silly that question is
Just ASK
- Don't assume anything, have absolute clarity of your work before you start.
- A minor communication gap will ruin your entire hard work so keep asking questions.
- No matter how dumb you sound
- No matter how silly that question is
Just ASK
- Don't assume anything, have absolute clarity of your work before you start.
- A minor communication gap will ruin your entire hard work so keep asking questions.
2. Don't jump straight into coding
- Pick a pen and paper, and solve it first.
- Understand how the data is flowing in your code.
- Analyse each and every aspect of the given functionality.
- See if it impacts other modules.
- Pick a pen and paper, and solve it first.
- Understand how the data is flowing in your code.
- Analyse each and every aspect of the given functionality.
- See if it impacts other modules.
- Identify any blind spot in your work and get proper visibility of that area.
- If required, discuss your proposed solution with your peers. They might suggest an alternate way.
- It might sound time-consuming but in fact, it's a time saver.
- If required, discuss your proposed solution with your peers. They might suggest an alternate way.
- It might sound time-consuming but in fact, it's a time saver.
3. Stop Optimizing in the First Go.
- First Solve the Problem
- Then divide the problem into multiple steps, and try to optimize each step independently
- Then combine them to get the optimized solution
- First Solve the Problem
- Then divide the problem into multiple steps, and try to optimize each step independently
- Then combine them to get the optimized solution
4. Limit the use of Debuggers
- Dry run your code, meaning run the code in your mind or paper first. Try to analyze the possible output of it without actually running the code.
- Analyse each line written, try to guess the input and output of the code, and test it in your mind.
- Dry run your code, meaning run the code in your mind or paper first. Try to analyze the possible output of it without actually running the code.
- Analyse each line written, try to guess the input and output of the code, and test it in your mind.
- Relying too much on a debugger will actually paralyse your brain in the long run
- Remember that the production system will not have debuggers; the day production breaks, you will need to quickly analyse the issue and rectify it, and no debugger will come for your help.
- Remember that the production system will not have debuggers; the day production breaks, you will need to quickly analyse the issue and rectify it, and no debugger will come for your help.
5. Don't wait for QA to Report your Bug
- "Ok, Happy scenario is working my job is done as a developer" - the wrong way to approach your work.
- If a user story is critical, complicated or affecting multiple modules then do whatever is required to test your work.
- "Ok, Happy scenario is working my job is done as a developer" - the wrong way to approach your work.
- If a user story is critical, complicated or affecting multiple modules then do whatever is required to test your work.
- Nobody is going to tell you the basics you need to judge it as a programmer.
- Literally, test as QA because as a developer you know better which modules are got affected, and which part is changed so test everything which is appropriate according to you.
- Literally, test as QA because as a developer you know better which modules are got affected, and which part is changed so test everything which is appropriate according to you.
6. Asking for Help in the Right Way
- Before you call somebody to help you, make sure you've tried all the possible ways from your end.
- When asking for help list all the ways which you already tried with their results.
- Before you call somebody to help you, make sure you've tried all the possible ways from your end.
- When asking for help list all the ways which you already tried with their results.
- This will immensely help another person to understand the issue at its deepest level and it will speed up the process.
- Remember you got to respect their time so do your homework before asking for help.
- Remember you got to respect their time so do your homework before asking for help.
That's it for now!
If you loved reading this, then you might also like reading my previous thread.
If you loved reading this, then you might also like reading my previous thread.
Namaste, I'm Vikas
I write a thread on Backend Development every Mon, Wed & Friday.
1. Follow me @vikasrajputin to read all my future threads
2. RT the start of this thread mentioned below to help it reach others
I write a thread on Backend Development every Mon, Wed & Friday.
1. Follow me @vikasrajputin to read all my future threads
2. RT the start of this thread mentioned below to help it reach others
جاري تحميل الاقتراحات...