4 ms·
Productivity and efficiency of people is one of the topics that's always fascinated me, and I've both read a lot of material on the topic and have had the oppor
by jiggawatts 6y ago
Productivity and efficiency of people is one of the topics that's always fascinated me, and I've both read a lot of material on the topic and have had the opportunity to observe hundreds(!) of organisations first hand thanks to being a consultant roaming from place to place.
From both scientific studies on the matter and anecdotal observation of the same, I can unequivocally state that the top three priorities are:
#1) The high-level goals of the organisation must be rapidly and clearly passed down the management hierarchy so that everyone can "row in the same direction". Ambiguity about goals, or uncertainty in whether one's work is even worthwhile is an astonishingly effective destroyer of productivity. Never treat employees on a "need to know" basis, feeding them the bare minimum that you think they need.
#2) There is no known method more effective at improving overall product quality than mandatory peer review of all code. Not only does this have the obvious direct benefit, but it also helps cross-train senior staff, bring junior staff up to speed, and helps improve consistency.
#3) There is no known method more effective than checklists at improving the quality of manual processes. Sure, if you plan to do something a hundred times, automate it. But you know what is really easy to turn into automation? A checklist. For non-automated processes, a checklist allows junior staff to confidently produce quality. Checklists are a training aid as much as they are a tool for quality improvement.
Of course, there's a very long tail of things one can do on top of those basics to improve productivity, especially of junior staff. Use an IDE. Use a code linter. Use automatic tests on checkin. Etc, etc... But none of those hold a candle to the above three in terms of raw effectiveness.
To put things in perspective: I'd rather have those three things and no source control than source control and none of those three things. You can meticulously track every version of a piece of garbage and it'll still be garbage...
- xyzelement 6y agoI agree with #1 and #2 and will add the following: #1 - on the flip side, you need employees who give a shit about your company mission and your clients. Just like a good organization is eager to share these goals, a good employee is eager to receive them. Whenever someone doesn't care, it's a big indicator to write them off. #2 - Likewise, people have to give a shit and be critical. I used to run code reviews on my team like this - person A reviews person B's code (together, in person) and I sit behind them, not to judge B's code but to judge A's review. It's shocking to me how people want to give code "the benefit of the doubt" and don't flag things unless they are truly egregious. It doesn't help anyone when people hold back like this.
- seer 6y agoVery good points and eloquently put. I want to add something though regarding #2 - having a code review process is not enough. You need to train people how to do good reviews. I’ve seen countless times people treat reviews “an approval” by both author and reviewer and for various reasons. People don’t consider it worthwhile, or they don’t want to offend, or they feel offended. There is countless amounts of advice out there on how to write good code. But there is precious little on how to review code, and even less on how to write “reviewable” code, which is also a thing. But if people understand the PR review process as more of a conversation, meant to align people on one direction, PRs are incredibly awesome.
- hallqv 6y agoLiked your post, do you have any reading recommendations on the subject?
- randomsearch 6y ago+1 excellent advice, please take the time to add references if you can.
- jiggawatts 6y agoI would really like to, but some of these references are papers I had come across a decade ago, so it would be difficult to track down. I don't research this stuff formally, it's just something I like to read up about. I did manage to track down this New Yorker article: https://www.newyorker.com/magazine/2007/12/10/the-checklist https://www.newyorker.com/magazine/2007/12/10/the-checklist I know it's not exactly Nature, but the point made stands, and I did track down some papers related to error rates and different methodologies used to reduce them. There's a reason surgeons and pilots both use checklists. It's because a failure of quality in their profession kills people. Lives don't have to be at risk for quality to matter!
- hipjiveguy 6y agoI've brought this up at work many times, and even had a team adopt it for a 6 month period - but there were so many people on our team that didnt want to do the work of filling out a simple checklist, it was amazing. Great idea, and this is one of the few books I truly remember, and try to apply, all the time (Checklist Manifesto) !
- jiggawatts 6y agoI use literally just Notepad, because it's always available on every Windows desktop and server. On my laptop I use a decent text editor, but trust me, Notepad is sufficient. I have a simple style that is easy to fill out: [.] Commenced high-level task. [o] Completed sub-task [.] Incomplete sub-task [ ] Not yet started [-] Cancelled or not-applicable [?] May not need doing at all, or pending advice [!] Issue or error [ ] Include command-lines under the tasks: wget https://test.com/foo [o] Record output after the tasks if needed -- "Task ID: 929123" Of course, the aim is to slowly convert something like this into a script or a service desk workflow. In my experience, it's almost impossible to correctly automate a complex, high-level task given no other information that its English description, such as "build a new web server for a developer". However, if you've built 5-10 such servers manually, diligently recording the tasks in a checklist each time, then the script practically "jumps out at you"... As a practical example, most engineers will say that to install a new physical server (not including the OS) is about 5-10 steps. I counted 50-100 after developing a checklist! E.g.: Did you remember to: Check that the firmware version matches the version of the other servers in the same cluster? If not, did you update it? Check the NIC firmware too? RAID firmware? System time, date, and time zone? Secure erase / factory reset the BIOS? Upload an SSL certificate for the management port? Register it in DNS? Register it in the CMDB? Register it in system-management software? Burn-in test the memory? Configure LACP on the NIC? On the switch too? I have personally witnessed major issues, even outages, caused by the above being skipped by careless engineers. "Oops."