1. Knowledge is power. So for an experienced person how much more knowledge he has whether it is domain or technology that much he will receive value from the market.
2. For a senior developer handling the complex situations by his own ability is what makes him powerful.
3. See the things with wide perspective always to analyze all the conditions.
4. My Maya is to live life in my own way so the way to live life is nothing but my Maya.
Apni Maya banaao kisi ko thagne k liye nahi. Balki khud ko aur sabko ek swasth life jine k liye.
Maya means kya? Maya means an imaginary layer of environment formed from memories and experiences. For example, talk nicely to people? because as per experience if we talk good to people they will be nice to me as well and we can pursue a healthy relationship and We can do a healthy business also. So talking nicely is a part of Maya like that only giving suggestions to people when they are confused or they wanted to discuss. These all small help or involvement of yourself towards people businesses makes them good customers for you. Maya should be like imaginary haveli based upon memory and experiences. You have to create it because nobody else can create a better Maya for you other than you. For example, A child creates a cry Maya to convince his mother that he is hungry. Maya is colorful, Beautiful, Greenness, Freshness etc. Your Maya Should have boundary according to the situation.
Maya involves your
Thinking,
Feelings,
Creativity,
Imagination power,
Fast Pace and well-mannered Communication,
Fast Pace understands the thing and replies back,
Dressing Sense,
Eating Sense,
Working attitude,
Sitting/sleeping/standing posture,
etc.
5)What kind of mistakes may happen by an experienced guy like it could some special scenario missing or some kind of spelling mistakes.
What never should happen is application level mistakes.
6)Create a document and put logic into them.
7)Determine the impacted areas of my code.
8)Begining work looks like straight forward but in mid it becomes complex. So don't estimate time at the beginning after working on 10% then decide estimation and give it to concern person.
A good developer is always a good time estimator.
9)Mention detail in the tracker for which reason I took more time.
10)Feel the holistic confidence in own written code.
11)Connect everything and then test not only limited to own work.
12)Not putting the effort in a proper way.
13)Help to the senior developer as a team.
14)Self-thinking + Own the code + Do argument + Seniors may be wrong + Document can be wrong.
15)See challenges while time estimation.
16)Tell (suitable) senior at the beginning of work if not understanding.
17)Keep looking other's code to analyze the over all picture of our product + functionalities.
18)How to solve not understanding sub method work:
Debug the sub method + Read document/comment of that code + Contact owner of that code.
19)Shreeja situation, not proper communication among the team resulting the in delay in integration and submission.
20)Discuss the impacted areas with seniors and Testing team.
21)Be a leader of your work know always more than you senior knows about the work.
22)
As the days go:
1)plenty of knowledge should grow.
2)decision power on the product/flow should grow.
3)Enjoyments should grow.
4)communication on the product/flow should grow.
23)Thinking about time in life should become be like we have to achieve/see a lot of things and we have less time to do that.
24)Create a dream and consistently follow it. Recall it in each morning. The more you think about it the more near you will reach towards it. Don't let it die.
25)Learn the art of self controlling mood and art of time utilization in all the situations.
26)The purpose of living should be earning knowledge all the time and from all the ways.
2. For a senior developer handling the complex situations by his own ability is what makes him powerful.
3. See the things with wide perspective always to analyze all the conditions.
4. My Maya is to live life in my own way so the way to live life is nothing but my Maya.
Apni Maya banaao kisi ko thagne k liye nahi. Balki khud ko aur sabko ek swasth life jine k liye.
Maya means kya? Maya means an imaginary layer of environment formed from memories and experiences. For example, talk nicely to people? because as per experience if we talk good to people they will be nice to me as well and we can pursue a healthy relationship and We can do a healthy business also. So talking nicely is a part of Maya like that only giving suggestions to people when they are confused or they wanted to discuss. These all small help or involvement of yourself towards people businesses makes them good customers for you. Maya should be like imaginary haveli based upon memory and experiences. You have to create it because nobody else can create a better Maya for you other than you. For example, A child creates a cry Maya to convince his mother that he is hungry. Maya is colorful, Beautiful, Greenness, Freshness etc. Your Maya Should have boundary according to the situation.
Maya involves your
Thinking,
Feelings,
Creativity,
Imagination power,
Fast Pace and well-mannered Communication,
Fast Pace understands the thing and replies back,
Dressing Sense,
Eating Sense,
Working attitude,
Sitting/sleeping/standing posture,
etc.
5)What kind of mistakes may happen by an experienced guy like it could some special scenario missing or some kind of spelling mistakes.
What never should happen is application level mistakes.
6)Create a document and put logic into them.
7)Determine the impacted areas of my code.
8)Begining work looks like straight forward but in mid it becomes complex. So don't estimate time at the beginning after working on 10% then decide estimation and give it to concern person.
A good developer is always a good time estimator.
9)Mention detail in the tracker for which reason I took more time.
10)Feel the holistic confidence in own written code.
11)Connect everything and then test not only limited to own work.
12)Not putting the effort in a proper way.
13)Help to the senior developer as a team.
14)Self-thinking + Own the code + Do argument + Seniors may be wrong + Document can be wrong.
15)See challenges while time estimation.
16)Tell (suitable) senior at the beginning of work if not understanding.
17)Keep looking other's code to analyze the over all picture of our product + functionalities.
18)How to solve not understanding sub method work:
Debug the sub method + Read document/comment of that code + Contact owner of that code.
19)Shreeja situation, not proper communication among the team resulting the in delay in integration and submission.
20)Discuss the impacted areas with seniors and Testing team.
21)Be a leader of your work know always more than you senior knows about the work.
22)
As the days go:
1)plenty of knowledge should grow.
2)decision power on the product/flow should grow.
3)Enjoyments should grow.
4)communication on the product/flow should grow.
24)Create a dream and consistently follow it. Recall it in each morning. The more you think about it the more near you will reach towards it. Don't let it die.
25)Learn the art of self controlling mood and art of time utilization in all the situations.
26)The purpose of living should be earning knowledge all the time and from all the ways.
No comments:
Post a Comment