Two weeks ago I covered the benefits of building a good team and how it pays off once you get over the initial hurdles, which require engendering a level of trust, ownership, and confidence in those around you. This week I want to focus more specifically on how using the right tools can aid and accelerate this process.
IBM is having another heart attack, HP is falling apart, and those crashing share prices are a dose of reality to those buy innovative companies and process them into a business unit shops. Now the bad ideas are getting shed and creative destruction continues in the marketplace. This darwinism is accelerated in software and technology because anybody with a computer can potentially wreck your business tomorrow morning. Your software becomes obsolete, your product antiquated, and your board members suddenly start a share buyback programme to support their stock options.
The RhodeCode infographic charts how we got to where we are today. From Marcin’s initial idea to a rapidly growing software development company creating the world’s best software development solutions.
Team work is not a skill, it is a philosophy that you develop and it becomes part of who you become. Depending on how you decide to bring your team player mentality to work, you will either be a great benefit to your colleagues, engendering a situation where both you and others can perform to their best and create a positive and productive work place, or you will be a myopic, probably narcissistic, ego-centric person lacking the self-awareness to make a positive difference. You are on this imaginary scale of extremes, every single day, if you work with other people.
This week I cover for the third and final time - code review. The direction of this weeks blog comes from our very own coder supreme Sebastian Kreft who pointed me in the direction of a case study done on NASA best practices used to develop the code that landed the Curiosity Rover on Mars.