Hacker News new | past | comments | ask | show | jobs | submit login

That's what I did at my last job, now I mostly feel like that was a mistake. I was the guy contributing 90% of the wiki knowledge, for no real appreciation or incentive. And when something I posted inevitably become out of date and caused a problem for someone, guess who got blamed? I feel like I was enabling the team's bad habits.

At $NEW_JOB I'm just putting everything into my Obsidian repo. It's great because I have complete freedom to refactor my notes however and whenever I want. When someone has a question for me, I just look up the answer in my notes and send it over to them. Then they'll copy it into their OneNote, and everyone is satisfied.

This isn't my ideal world, but this seems to be the state of equilibrium when management doesn't lay down any expectations or incentives.




Interesting story about where blame is placed, and your move to Obsidian. Thanks for sharing.

I've actually done something similar to your Obsidian repo: I put all my notes into markdown and publish them with mkdocs[1]. This gives me the same editorial control and freedom from blame as your notes, but mine are public by default, so I can still simply reply with a link. I just can't post anything that is sensitive, which hasn't been a significant drawback yet. I have considered moving to an Obsidian based system, but have yet to find something compelling enough to make the switch. It looks like an awesome app though and is still on my radar.

1. https://danielhoherd.com/tech-notes/exiftool/


This is a perfect example of poor organizational incentives.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: