Earlier I wrote on how to become a better programmer, Wake up one morning after having a revelation; you decide to do one good thing in your life, instead of your usual rant. I thought, Well I’ve been to Jacas recently at work, and I want to start being nice to others. Maybe I was too harsh on recruits and, I did not want to make them cry on the first day. You just have to pay attention because this is important.
You just have to pay attention because this is important.
Escape from the cave
Hey if you are still programming as you live in the cave, hide stuff for yourself or idealizing abstractions and minimize the effort of others, bragging yourself out as you program god with 100X productivity or what you want to call it, please stop it before proceeding.
Acting like this will not get you more. Cave man will always be in other people’s eyes.
Nothing different instead. View your code, share your opinions, do not reduce other different ideas of your own and stop calling yourself for the first time product.
This will help you follow the following advice.
To be a role model
Of humility. Being humble is not a bad thing. You will not only love the best, as you might imagine but will also be more efficient. It will appreciate you more agility, and you will probably be less biased from your actions.
Of business ethics. It is important to keep your safety when you are always asked to provide constructive and honest comments. You need to act with responsibility for your actions. Do not hide the staff under the carpet do not think others near you will not notice. This will help you create a stunning area when people are around you.
Be an active member of the team
Programmers become more efficient and productive in creating software by improving their ability to understand, communicate with, and collaborate with others.
By building confidence. If people trust you will help you. If not I will ignore you. Trust is not assumed. This may be the hardest part for some people.
By showing respect. You are not alone. Before you enter the action, drop your ego to the ground. You will be criticized as well as receiving a lot of criticism, so you better learn how to accept it. Even if they come from newer team members, with less experience than you. You have to show respect and listen. Practice on your formulas. Instead of saying “oh this stupid” or “this is crap” start talking about “confusing factors” or “it’s not clear that way, maybe if you can do it differently.” Discuss not attack.
By living in the earth, not in the sky. No one likes the smart ass. Be humble and do not provoke your teammates with meaningless arguments. Remember, you’re a human being and not Superman. Instead, build on your social skills. Have fun by being a real person.
Software development is a team effort. There was not one piece of successful software built by people. Drop the ego to the ground and begin to take responsibility. If you follow the next advice you will check Legacy mode.
Be a leader
You do not learn much if you work alone.
Of team culture. Value code review, development-driven testing, right design documents, and social group events. Maintain a spirit or list of principles that everyone must respect and defend. Otherwise, it would be chaotic chaos and one more shouting than prevailing. Max world will be made with a lot of aggression, sadism, and randomness.
Of performance. Promoting development driven by consensus. This may mean you may turn some operations from start to finish, or you just give grab people out of their offices if you think the process is leading to a stop. By catching the course means to be on top of any problems. Make sure you grab the right people at the right time.
Working alone is more dangerous than working with others
Focus on people as much as they focus on your code.
A 10X programmer with 10x-peoples skills is an obstacle.
Any amount of intelligence or knowledge can replace the spirit of a good working group.
Building a health software development culture is more like an art than a feature because it only depends on the real interactions between the teams. The absence of those is like wood and steel binding together with glue. No matter how glue applied, it will eventually break.
Skilled leaders serve their teams, not vice versa.
It is also wise to make it very easy to take advantage of the situation and fulfill its agendas.
Large software shipping requires the formation of extensive relationships first.
This applies to any goods subject to purchase involving cooperation, not just to programs or services.
I hope you take it on board on your next social interaction. Until then I wish you an excellent fare.
Please share this post and get upset with my other articles.