Tag Archives: productivity

Type 1 vs Type 2 Workers – Quora Answer

If you’re a worker in a village who supplies said village with water, you are valuable to its people. There are two types of workers: Type 1 worker: Grabs an empty bucket or two, goes to the sweet water lake, fills them up, comes back and makes twenty people happy. He gets to drink some of that water along the way, and once he gets back, takes some of the water home.

 

Type 2 worker: Disregards how much of a “fair share” of water he’s getting. Instead of grabbing a bucket, grabs a shovel and a little cup, and disappears for a while. He’s digging a stream from the lake towards the village. Often he disappoints people for having returned from weeks of work with an empty cup. But the elders in the village for some reason believe in him and want to keep him (and throw him a bone so that he doesn’t starve for a little while). Some day, suddenly he shows up with a constantly flowing stream of water behind his back. He puts the Type 1 workers out of water delivery business. They’ll have to go find a different activity and “team” to work with. Type 2 worker, depending on how much control they retained on that stream, get to own a good chunk of it. Because the village wants to acquire and integrate that stream, they compensate the ownership of Type 2 worker in that stream with on par ownership in the village itself, typically land or such.

(Full Story: http://ift.tt/1gzIpXK )

Unlocking the Power of Stable Teams with Twitter’s SVP of Engineering

1. Build strong teams first. Assign them problems later. 2. Keep teams together. 3. Go modular. Remove dependencies. 4. Establish a short, regular ship cycle.

(Full Story: http://ift.tt/1g6gCwC )

Killing the Crunch Mode Antipattern – Chad Fowler

In the software industry, especially the startup world, Crunch Mode is a ubiquitous, unhealthy antipattern. Crunch Mode refers to periods of overtime work brought on by the need to meet a project deadline. Developers stereotypically glorify the ability and propensity to stay up all night grinding through a difficult problem. It’s part of our folklore. It’s part of how we’re measured. It’s something companies and leaders take advantage of in order to accomplish more with less. And it’s stupid.

(Full Story: http://ift.tt/1arPI4u )

High costs and negative value of pair programming

The economics of pair programming are severely negative. Pair programming costs were $7,576 versus $2,841 for an increase of over 266%. Pair programming schedules were 11.11 days as opposed to 8.33 days for an increase of 133%. Unless the quality results for the pair approached zero defects and the quality results for the individual programmer were very poor there would seem to be no economic justification for pair programming. Unfortunately the quality data from the pair programming literature is not adequate because it omits the impacts of inspections and static analysis.

(Full Story: http://namcookanalytics.com/high-costs-and-negative-value-of-pair-programming/ )

Vagrant | Fly Dillon Fly

We needed to ensure that all developers ran environments that were the same in all practicable ways to production. This meant: The same version of CentOS The same version of PHP The same version of Apache The same version of Memcached The same version of MySQL The same Apache modules The same webroot The same folder permissions The same log directories The same. The same. The same.

(Full Story: http://flydillonfly.wordpress.com/2012/11/22/vagrant/ )

Boxen is a framework for managing almost every aspect of your Mac

Boxen is a framework for managing almost every aspect of your Mac. We built a massive standard library of Puppet modules optimized for Boxen to manage everything from running MySQL to installing Minecraft. We designed Boxen with teams that work like GitHub in mind. Boxen automatically updates itself every run and opens and closes GitHub Issues as problems arise and get fixed. With Boxen, we treat our development environments with the same care we give production: we test our code and rely on Continuous Integration to deploy changes.

(Full Story: https://github.com/blog/1345-introducing-boxen )

Sage Advice for Young Employees Early in Their Careers

1. Don’t expect constructive feedback without asking directly for it.
2. You won’t really have a mentor unless lightening strikes.
3. People won’t communicate expectations clearly (you must ask, clarify, ask again).
4. Constructive criticism stings, but we all need it.
5. Don’t overly rely on HR. Make your boss and her boss your primary allies.
6. Show up early.
7. Be humble.

(Full Story: http://www.bothsidesofthetable.com/2012/12/10/some-quick-sage-advice-for-young-employees-early-in-their-careers/ )

The Technium: The Post-Productive Economy

hypothetical choice between option A and option B.

With option A you are allowed to keep 2002 electronic technology, including your Windows 98 laptop accessing Amazon, and you can keep running water and indoor toilets; but you can’t use anything invented since 2002. Option B is that you get everything invented in the past decade right up to Facebook, Twitter, and the iPad, but you have to give up running water and indoor toilets. You have to haul the water into your dwelling and carry out the waste. Even at 3am on a rainy night, your only toilet option is a wet and perhaps muddy walk to the outhouse. Which option do you choose?

(Full Story: http://www.kk.org/thetechnium/archives/2013/01/the_post-produc.php )

Follow

Get every new post delivered to your Inbox.