Thanks for the talk! I was noted for "liking documentation" when I took a task to relocate our docs to a more convenient place. I wasn't sure how to take that, as I thought everyone should like documentation! Writing it down is a great way of retaining and transfering information. I've seen a case myself where poor documentation of an issue caused fixes to be removed and replaced later when the defect re-appeared.
Did the switch from Angular -> React improve the documentation experience? Was this response based on other factors as well?
Hey Ben, adding a short answer here, I know we covered it on the panel, in short yes and no, it allowed us to do some interactive components and improve the user experience, but from a contributor perspective not really. The other consideration was that we had React devs that could help develop and maintain as opposed to not having Angular experts anymore, so that swayed our decision too, that's not to say we don't have love for Angular anymore!
Thanks for the response! It was exciting to have my question be asked while watching. Using the already existing skillset seems to be the theme to some of the discussion throughout Codeland. I fall into that pitfall where I want to branch out with a new idea with a new technology, and it just doesn't mesh well. Capitalizing on the experience already there is the clear answer!
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
For further actions, you may consider blocking this person and/or reporting abuse