this post was submitted on 11 Apr 2024
321 points (97.9% liked)
Technology
58013 readers
3348 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
When I was a student I never understood how something like this could happen. "Just rewrite it" I thought, how hard can that be. But working in a corporate environment I now totally understand it. Everything you write will at some point become part of code that, to the fast majority of colleagues, will just be a black box that they've never touched and don't intend to. Despite my urge to test and document everything, I've already more than once complained about my own code, only realizing later that I wrote it myself. Often you can still find out what it does, but the "why" gets lost and because of that people are afraid to change it.
I feel like this is what gets lost whenever documentation is talked about. Yes, you should probably be able to work out what something does by looking carefully at it - but why can be so easily lost!
Well I suppose that reminds me, I ought to comment the why and the where a bit more lol
Or there was documentation. You even remember reading it.(Or writing it) But since then we've changed from shared folders to SharePoint to something else, and reorganized folder hierarchy at least five times. I have no idea where to find it, or if it was purged in one of the cleanups.