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 ๐๐
Either that or use git. If you fix a bug, be sure to add a good description of the bug in the commit message; then, in the future, you can just use git log --grep "<error message>" to look through the commit history and find all the relevant information, including how it was fixed back then, who did the fixing (and might therefore know more about it), when that was, etc.
Yes, your right.. Both r the good option to have but to have is the first step and the important step to maintain the documentation for errors๐๐.. Thank you for sharing your experience...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I like this tip a lot! I mentioned in one of my articles about coding interviews, but you can apply it to other contexts.
I just found one I wrote while I worked at Amazon. Iยดll share it soon.
Thanks for sharing!
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.?
I'm glad that you find it useful ๐๐.. Sure I can wait for ur version
Either that or use git. If you fix a bug, be sure to add a good description of the bug in the commit message; then, in the future, you can just use
git log --grep "<error message>"to look through the commit history and find all the relevant information, including how it was fixed back then, who did the fixing (and might therefore know more about it), when that was, etc.Yes, your right.. Both r the good option to have but to have is the first step and the important step to maintain the documentation for errors๐๐.. Thank you for sharing your experience...