Explore >> Select a destination
|
You are here 
|
icreatedocs.wordpress.com | ||
| | | | |
accessibledreams.home.blog
|
|
| | | | | In October I attended and spoke twice at Microsoft TechDays in Stockholm, Sweden. As I made the engagement to make a blogpost of each conference that I attend as a speaker or as an attendee I give you a rewrite. And I know 23rd and 24th of October is a while ago. But Last month... | |
| | | | |
blog.jetbrains.com
|
|
| | | | | Write the Docs Portland Not that I can judge, as I'm not a frequent conference-goer, but Write the Docs (WTD) stands out from all others I have attended - the good, the bad, and the corporate.& | |
| | | | |
passo.uno
|
|
| | | | | Just around the time I was complaining about the scarcity of books on technical writing, I got a copy of Technical Writing for Software Developers by Chris Chinchilla, a regular of the Write the Docs community. Delighted by the chance of reading a book from one of the sharpest pens in technical writing, I set aside some time to read through the nine chapters and write a review. The book taught me little I didn't already know - Chris and I use the same tools and methods. The biggest value I extracted from TWfSD is its reflection of the times: it spurred lots of thoughts on the future of our profession and how we promote it. | |
| | | | |
blog.sentry.io
|
|
| | | Learn about why we need rate limits, the absence of standards for HTTP status codes and response headers, and three ways to handle rate limits in code. | ||
