Re:The Lone Developer Problem
by owyn on Monday February 27, 2023 @11:50PM
(#34965755)
This is great! I don't know if I'll have a project that I expect to last long enough to worry about bus factor, most of the work I do is either throw away stuff for myself or already part of a large shared team effort. But I love the idea. It's long but I skimmed it quickly and I think it's got a very good level of detail and is overall very readable with just the right amount of snark. :)
[ Parent
| on HN ]
Re:The Lone Developer Problem
by gavinhoward on Tuesday February 28, 2023 @12:01AM
(#34965818)
Thank you so much!
I wrote it in snatches of time nearly always late at night, so the snark just...happened. I was worried how it would be taken, so thank you for the encouragement, including about the level of detail.
Re:The Lone Developer Problem
by JoelMcCracken on Tuesday February 28, 2023 @12:27AM
(#34965969)
I love it, I think I’m going to take some of these ideas for a literate programming thing I’m working on. Also props for proving that jagoff wrong.
Level of detail is something I think a lot about lately. Interviews go off the rails with candidates who answer in too much detail or not enough. Meetings go off the rails with non-actionable proclamations or tedious line-by-line details.
Machine generated / doxygen / javadoc documentation is the worst. I'd rather read the code, but code can also be difficult to read even if it's functional, especially when it's optimal. So having a guide to the code written by someone who knows how it is all laid out is pretty much the best case scenario.