News for hackers. Stuff that matters.
Re:What senior engineers do: fix knowledge holes by Waterluvian on Saturday July 20, 2019 @06:08PM (#20488665)
I hear you. But I'm not convinced that there's ever an okay time to skip writing down design, requirements, etc. Even if they're rough in a wiki page and it takes 30 minutes. It simply doesn't belong in your head alone.

I'm certainly not advocating for adding insane amounts of process to little jobs. But show your work. It's worth most of the credit.

Re:What senior engineers do: fix knowledge holes by closeparen on Saturday July 20, 2019 @06:28PM (#20488735)
Sure, the author needs to write things down; often commit messages and block comments are enough, sometimes more is needed. If anything we are heavily under-invested in solo documentation-writing.

What drives me up the wall is starting a long, formal document and having a bunch of meetings about it, seeking input and consensus from 10+ people and committees, for something with the scope of a couple days. That process is designed for large, multi-engineer-month new systems, or decisions that will be hard to back out of and have ramifications for hundreds of people over years. But I often see junior engineers putting the wheels in motion for basic day-to-day maintenance and feature iteration tasks.

It doesn't help that our promotion process incentives this heavily, because it generates lots of evidence for the committee to evaluate.