#9 of 29-Oct '15 ___ _ ___ _ _ _ _ | _ \___ __| |_ / __|__ _ _ __(_) |_ __ _| (_)____ __ | _/ _ (_-< _| (__/ _` | '_ \ | _/ _` | | (_-< ' \ |_| \___/__/\__|\___\__,_| .__/_|\__\__,_|_|_/__/_|_|_| |_| The Economy Of The Future? At the heart of this change is information technology: a revolution that has the potential to reshape utterly our familiar notions of work, production and value; and to destroy an economy based on markets and private ownership. Almost unnoticed, in the niches and hollows of the market system, whole swathes of economic life are changing. Goods and services that no longer respond to the dictates of neoliberalism are appearing, from parallel currencies and time banks, to cooperatives and self-managed online spaces. Vast numbers of people are changing their behaviour, discovering new forms of ownership, lending and doing business that are distinct from, and contrary to, the current system of state-backed corporate capitalism. IMG:001-capitalism.png http://www.socialeurope.eu/2015/10/postcapitalism-the-economy-of-the-future/ https://www.youtube.com/watch?v=rrzXIV8eZPo _ _ | |_ ___ __ _ _ __ __ __ _____ _ _| |__ | _/ -_) _` | ' \ \ V V / _ \ '_| / / \__\___\__,_|_|_|_| \_/\_/\___/_| |_\_\ Don’t Destroy Your Dev Team By Growing That just someone IMHO I would say Take the time to grow sustainably Hiring at a pace faster than 1 new member per team every month puts a huge strain on the rest of the team. Not only does it drain your team’s time, but it can also increase the amount of time it takes for new members to become productive. Ensure team cohesion Be as open to letting people go who detract from team cohesion as quickly as you would for technical reasons. It’s that important. This doesn’t mean fire people who don’t want to go to lunch with you, but if the team needs to walk on egg shells around a member, that member is probably not worth having around. Spend time ensuring new member success Take an interest in their opinions and ask how they did things at their previous job. In short, make them feel like part of the tribe. Maintain a good ratio of senior to junior I believe the ideal ratio for senior to junior engineers is three senior to one junior engineer/ Be open to improvements Just because you want a new member to become “part of the tribe”, doesn’t mean you can’t learn new things from them Maybe they have advice on how to structure a sub-project more efficiently because they ran into that at their last gig. Maybe they have experience with an idea you’re just now starting to experiment with and can help you short cut most of the pain. Maybe it’s some other suggestion that you hadn’t thought of. You didn’t hire this person because they were a clone of you; take advantage of the infusion of this new “work energy". In the same way that adding carbon to iron makes it stronger, becoming a melting pot of talent will make your team stronger. IMG:003-sonic.jpg https://medium.com/swlh/don-t-destroy-your-dev-team-by-growing-eef50d83090e _ _ _ _ ___ ___ _ _ (_)__ | |_ _ _ __ _ __| |_ ___ _ _ | |__ ___ __ _ _ __ ___ (_-