How I, a beginner developer, read the tutorial you, a developer, wrote for me

Re:How I, a beginner developer, read the tutorial you, a dev... by BossingAround on Monday September 22, 2025 @09:37AM (#45333310)

It's not very crazy to me. Most corporate teams are overrun with feature creep that "is very simple" (i.e. it takes 3x as long as estimated, because the codebase is a mixture of overengineered spaghetti for that one customer with edge-case requirements and legacy, combined with tests that are meant to be run in a jenkins job which takes 4h to complete).

Then, the engineers are expected to write the docs in between these tickets, and doc is seen as something "to be done within 30 minutes" - of course the docs will be comically (or tragically, depending on your perspective) bad.

Most people have 0 idea on how to write good docs, so in 30 minutes, they write stream-of-consciousness docs and return back to the ticket hell.

[ Parent | on HN ]

Re:How I, a beginner developer, read the tutorial you, a dev... by ctkhn on Monday September 22, 2025 @09:40AM (#45333337)

Most places I've been could have been upgraded with stream of consciousness. It's not surprising that they aren't all perfect, and the one place that was done to a very high standard was properly overdone, but at most places whatever counts as onboarding docs either doesn't exist, is essentially unusable, or directs me to legacy things that on day one I don't know enough to not bother with

[ Parent | on HN ]