4 ms·
Yeah, if you're not focused, and you're not even writing documentation, there is no way you should be considered very good at your job. Early in my career I ha
by winrid 6y ago
Yeah, if you're not focused, and you're not even writing documentation, there is no way you should be considered very good at your job.
Early in my career I had someone that kept telling me "we don't write documentation because nobody will read it". I'll never put up with that again. You can take 30mins to write a confluence page describing the context, the solution, and comparison to other solutions and why this one was picked. It will save the company many hours later when someone else has to pick up your stuff.
- cameronfraser 6y agoDifferent companies have different needs, early stage startups would probably fire you for spending too much time on documentation because they're paying you to make progress on their product and you're usually working alone anyways or very small teams with heavy interaction. So not only would nobody ready it, it would become outdated within a month.
- dawnerd 6y agoAgreed, small teams could get easily dragged down by obsessing over documentation (and even testing to some extent).
- winrid 6y agoPeople think that documentation needs to be kept up to date. It doesn't. You don't have to always write docs saying "here's how this system works". You just write a document as a proposal saying "here is how I want to build this system". It takes 30mins. It helps everyone. If you want to change the system significantly, you just write another design doc. Also, if you do this you probably don't have to redo things all the time. If a company fires you for outlining how you're going to solve a big problem - they aren't going to do well anyway so you don't miss out on much. Based on my experience from a fast growing billion dollar company, and a company that you would call "fast moving" but will never be anywhere near as successful because they can't focus, let alone sit down for 30mins and write a document.