News for hackers. Stuff that matters.
Re:The 7 Habits of Highly Overrated People by foobarian on Thursday December 26, 2013 @02:25PM (#6967573)
I work at a company using something to this effect--when engineers get assigned projects they "own" them completely--from design and implementation to testing, deployment, verification, and bugs. We have a semi-formal tracking app with names attached to projects. There is never more than one person working on something. I think this instills a great culture of responsibility and accountability. It makes it very hard for someone to ride on others' coattails or not pull their weight, as you might get in a forced pair programming team, or a larger group.
Re:The 7 Habits of Highly Overrated People by pirateking on Thursday December 26, 2013 @02:41PM (#6967646)
Very interesting. Sounds like DRI (Directly Responsible Individual) at Apple. Are there any manager type roles (who does the assigning of projects to engineers)?
Re:The 7 Habits of Highly Overrated People by ionforce on Friday December 27, 2013 @06:14PM (#6973062)
How do you handle bus factor and what not? Or are you just saying... they're responsible, but other people are helping them?
Re:The 7 Habits of Highly Overrated People by foobarian on Saturday December 28, 2013 @04:12PM (#6976615)
Maybe it's not an issue because it's a web company, and it doesn't take a rocket scientist to ramp up on any given module or system in the codebase.

Typical flow handled by one person is about 3 weeks from start of coding to live code, and then a couple more weeks on followup, stats, bugs, etc. After that it's just part of the codebase and others can end up working on it; but they'd probably talk to the original author to get up to speed.