| | Why You Shouldn’t Use “Markdown” for Documentation (2016) (ericholscher.com) |
|
3 points by _xivi on Oct 6, 2023 | past | 4 comments
|
|
| | I Judge the Quality of Documentation in 30 Seconds (2014) (ericholscher.com) |
|
2 points by Tomte on April 27, 2022 | past
|
|
| | The Pac-Man Rule at Conferences (2017) (ericholscher.com) |
|
2 points by mooreds on March 30, 2022 | past
|
|
| | I Judge the Quality of Documentation in 30 Seconds (2014) (ericholscher.com) |
|
4 points by Tomte on Aug 23, 2021 | past | 1 comment
|
|
| | How I Judge the Quality of Documentation in 30 Seconds (2014) (ericholscher.com) |
|
1 point by Tomte on Jan 20, 2021 | past
|
|
| | You Shouldn’t Use “Markdown” for Documentation (2016) (ericholscher.com) |
|
2 points by oumua_don17 on May 29, 2020 | past
|
|
| | An Introduction to Sphinx and Read the Docs for Technical Writers (ericholscher.com) |
|
2 points by buixuanquy on May 6, 2020 | past
|
|
| | Using a Welcome Wagon to help first-time conference attendees (ericholscher.com) |
|
1 point by feross on Oct 3, 2019 | past
|
|
| | The Pac-Man Rule at Conferences (ericholscher.com) |
|
3 points by colinprince on May 10, 2019 | past
|
|
| | The Pac-Man Rule at Conferences (ericholscher.com) |
|
1 point by colinprince on April 30, 2019 | past
|
|
| | Why You Shouldn’t Use “Markdown” for Documentation (ericholscher.com) |
|
6 points by Cieplak on March 21, 2019 | past | 4 comments
|
|
| | Why you shouldn't use Markdown for documentation (2016) (ericholscher.com) |
|
19 points by throwawaymath on Nov 30, 2018 | past | 8 comments
|
|
| | How I Judge the Quality of Documentation in 30 Seconds (2014) (ericholscher.com) |
|
93 points by Tomte on Oct 5, 2018 | past | 59 comments
|
|
| | How I Judge the Quality of Documentation in 30 Seconds (2014) (ericholscher.com) |
|
3 points by Tomte on March 24, 2018 | past
|
|
| | One Percent for Open Source (ericholscher.com) |
|
18 points by walterbell on March 12, 2018 | past | 3 comments
|
|
| | One percent for open source (ericholscher.com) |
|
4 points by turoczy on March 9, 2018 | past
|
|
| | Don’t Use Markdown for Documentation (2016) (ericholscher.com) |
|
55 points by yinso on Feb 18, 2018 | past | 18 comments
|
|
| | “The post I never published,” a story about burnout (ericholscher.com) |
|
9 points by tbarn on Feb 7, 2018 | past
|
|
| | Breaking Cliques at Events (ericholscher.com) |
|
1 point by JoshTriplett on Dec 10, 2017 | past
|
|
| | A simple rule for breaking cliques at events (ericholscher.com) |
|
3 points by ericholscher on Dec 4, 2017 | past
|
|
| | The Pac-Man rule at conferences (ericholscher.com) |
|
1 point by ValentineC on Oct 24, 2017 | past
|
|
| | “My Code is Self-Documenting” (ericholscher.com) |
|
87 points by craigkerstiens on Jan 27, 2017 | past | 99 comments
|
|
| | Funding Open Source with Marketing Money (ericholscher.com) |
|
3 points by kawera on Oct 21, 2016 | past
|
|
| | Funding Open Source with Marketing Money (ericholscher.com) |
|
1 point by brechtm on Sept 1, 2016 | past | 1 comment
|
|
| | Don’t Use Markdown for Documentation (ericholscher.com) |
|
121 points by ericholscher on March 15, 2016 | past | 75 comments
|
|
| | Read the Docs goes full-time (ericholscher.com) |
|
3 points by jodal on Aug 8, 2014 | past
|
|
| | How I Judge the Quality of Documentation (ericholscher.com) |
|
123 points by craigkerstiens on Feb 27, 2014 | past | 73 comments
|
|
| | Read the Docs 2013 Stats (ericholscher.com) |
|
1 point by ericholscher on Dec 23, 2013 | past
|
|
| | Read The Docs: New theme & Improvements (ericholscher.com) |
|
18 points by abrahms on Nov 4, 2013 | past | 1 comment
|
|
| | Using ZNC, an IRC Bouncer (ericholscher.com) |
|
1 point by jrhorn424 on Oct 10, 2013 | past
|
|
|
|
More |
