Better not a self-document, but file it as ask for the inputs @ stack trace and suggest the solution too. It is easy to refer anytime, anywhere, build a reputation and you have global developers' attention too.
I also love error be properly put as JIRA issue(s), it helps as a stronger reference as long as you are in that company.
Thank you for sharing your opinionsππ.. And I think it's great if we can start documenting what we are doing daily.. it's a good habit.. It's very useful for us and we also find it easy we start doing documentain in the company ππ
Better not a self-document, but file it as ask for the inputs @ stack trace and suggest the solution too. It is easy to refer anytime, anywhere, build a reputation and you have global developers' attention too.
I also love error be properly put as JIRA issue(s), it helps as a stronger reference as long as you are in that company.
Thank you for sharing your opinionsππ.. And I think it's great if we can start documenting what we are doing daily.. it's a good habit.. It's very useful for us and we also find it easy we start doing documentain in the company ππ
When you say documentation, is it word doc, Evernote, etc or are u referring to any good developer tooling like JIRA etc.?