HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
sixhobbits
technical-writing
Productivity2017–2023
sixhobbits / technical-writing

technical-writing

A collection of materials relating to technical writing

Productivity
Explore on GitHubRead Hacker News discussions
2Distinct people
17Mentions
0Explicit recommenders
628GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A collection of materials relating to technical writing

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year17 dated mentions

Observed mentions: 2017-07-13 19:00:36 UTC to 2023-01-30 17:03:50 UTC.

024682017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC211
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC312
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC817
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101

What Hacker News says

17 sources
sixhobbits·Jul 4, 2022
Have you considered technical writing? I don't have experience with chronic pain but if you can still comfortably play video games maybe you can also write articles? I used to do this as a side gig and collected some resources and places that pay here [0] I have since started a technical publishing company [1] so it's a full time focus and most of our writers work 20h/week or less. Feel free to apply if it sounds interesting. [0] https://github.com/sixhobbits/technical-writing [1] https://ritza.co
In Ask HN: I'm disabled and out of money. Now what?
sixhobbits·Jun 25, 2022
We are running a course for exactly this! [0] Technically applications closed already but we will likely have some more space, or we will run another cohort soon so feel free to email me and I will try fit you in. I also keep a repository of my favourite books and some other resources here [1] And some very short advice we give to our writers here [2] [0] https://styleguide.ritza.co/writing-course/ [1] https://github.com/sixhobbits/technical-writing [2] https://styleguide.ritza.co/improving-your-writing/how-do-I-...
In Ask HN: How to level up your technical writing?
sixhobbits·Jul 23, 2020
I maintain a collection[0] of places with programs like this (I'll add lwn later today). As others have said, producing a good blog post takes time, so the money isn't as good as it initially seems if you aren't doing it for reputation or fun too. I also recently launched ritza[1] to scale production of this kind of content as it's definitely a growing demand trend. Happy to chat about technical writing with anyone - details in profile. [0] https://github.com/sixhobbits/technical-writing/blob/master/... [1] https://ritza.co
In LWN pays $300 for a well-written article from new authors
sixhobbits·Jun 1, 2020
I started by reading blogs. I wanted to contribute back to the same ecosystem that taught me so much (and I liked writing), so I started blogging about side projects on Blogger. I soon found Digital Ocean's writing program. They were paying $200 for blog posts, which was a lot as a student in South Africa. Money was fairly motivating, but soon the long and slow editing process got tiring, so I started freelance blogging for a few other sites instead. Then I created GitHub page[0] with links to places that pay for writing and links to some resources I enjoyed for learning how to write better. Now I'm convinced that the fact that more and more companies are paying amateur bloggers for content means that there's a nieche for more professionally written content, so (shameless plug) I launched Ritza[1] (I'm focussing on it full time from today
Read the rest
only, so it's still very rough!) [0] https://github.com/sixhobbits/technical-writing/blob/master/... [1] https://ritza.co
In Ask HN: How Do You Blog?
sixhobbits·May 12, 2020
Hey Philip, really great to see you run with this! I know you mentioned to me that this repository[0] where I try to keep a short list of publishers that pay for this kind of writing was an early inspiration and I'm still hoping to grow that list a lot after June when I spend more time focusing on technical writing too. As others have said, that's a really great looking list of interviewees. My only question is where this actually fits in to the rest of the book? It's not that clear from the Table of Contents. Could you comment on what percentage of the book is interviews, compared to writing advice? [0] https://github.com/sixhobbits/technical-writing/blob/master/...
In Show HN: Writing for Software Developers
sixhobbits·Feb 8, 2020
I had a similar question the other day. I asked a few people and no one seemed to have a good collection to point to. I specifically like reading posts by people who post regular retrospectives (weekly, monthly, or yearly). So I started [0]. It only has three entries right now (including the one you mention above), but I would love to see contributions via pull requests. [0] https://github.com/sixhobbits/technical-writing/blob/master/...
In Ask HN: What are good solo developer blogs that you enjoy reading?
sixhobbits·Jan 20, 2019
I'm surprised at how negative a lot of people are around tutorial writers. In my (biased) experience, tutorial writers are a) relatively good at what they do and what they're teaching, even if they're beginners and b) definitely not driven by "showing off" or "building their CV" motivations. Tech is hard. There is a lot of it out there. It's always changing. There are a lot of variables in terms of your set up and your needs. Maybe not every tutorial is going to solve your exact problem or remove all of your headaches, but imagine trying to work all of this stuff out without the amazing resource of records of other people trying stuff and taking time to explain. Apparently back in the day, this was done over email and IRC. You would wait days to get an explanation from someone and some code to try out, and spend days hacking at stuff tryi
Read the rest
ng to figure it out for yourself. Now you can find a tutorial that's specific to your needs and if you don't like it, you can read through 10-100 others. Tech is hard, and tutorials aren't going to fix that. You'll still have to battle through your issues, alternating between emotions of "this is impossible. I'm not competent enough" and "OMG it works this is amazing". That's most of programming. If you don't like that experience, it's probably best to pick a slower moving field. That's the "tech is hard" bit. Now writing. Writing is also hard. And because since school most people are put either into a "Arts" bucket or a "Science" bucket, very few people take time to figure out how sentence construction works and how to piece if statements together. It's quite admirable that people who have actively hated and avoided writing for most of their lives still see a gap and try to fill it by writing explanatory materials, usually for free. And then there's education which is hard even if you're good at writing and good at technology. The curse of knowledge is a big hurdle. Finding the correct balance between maintaining a focus on one thing and giving enough context to that thing that you're explaining is hard. So yes, I highly encourage everyone to get better at writing. Better at education. Better at technology. But to be good at all three is rare, and most of these people find they fit pretty well at universities as lecturers, where only a very limited number of students have access to them. If you're keen to help fix the problem that you point out, add your voice. Spend some time writing a high quality tutorial after you find the solution to a problem that you're having. Find time to edit the tutorial for good flow, bugs, and everything else that makes a tutorial frustrating to follow. I maintain a short list of technical writing and publishing resources [0], which I'd love to see more contributions to. I also write tutorials for CodeMentor [1], and a few other places[3]. Technical content is hugely valuable, so if you're interested in contributing, it's usually easy to find community editors at large sites who will give you free guidance and editing, and often even pay you for your content while letting you keep it under an open source license. If you want help or advice on how to write, this is an open invitation to contact me through Twitter or Email and I'll happily look over your drafts, discuss outlines, or generally help you become a better writer. [0] https://github.com/sixhobbits/technical-writing [1] https://www.codementor.io/garethdwyer/posts [2] https://dwyer.co.za/writing.html
In Ask HN: Why do tutorial writers combine 10 technologies when 1 or 2 would do?
sixhobbits·Jun 21, 2018
I read thousands of books, but never learned to write eloquently until I was 18 and was taught to write by someone very experienced at teaching writing. He went through dozens of essays with a red pen, tightening constructions and arguments. I'm convinced that doing is the only way to learn writing, and if you can get 1-on-1 guidance and detailed feedback, it can hugely accelerate the process. That said, also read * William Zinsser "How to write well". It's a very practical classic that improved my writing by a factor of two or more after one reading, and I found it enjoyable enough to read it more than once. * Mark Forsyth "The Elements of Eloquence". Also highly enjoyable while remaining very practical (it also took several readings to remember a lot of the points he made, but it's reasonably short and each of the many sections are inde
Read the rest
pendent, so it's easy to open it up and learn something in 2-3 minutes). If anyone is interested in the intersection of technology and writing eloquently, pull requests to https://github.com/sixhobbits/technical-writing/blob/master/... are very welcome
In Ask HN: How can I become more eloquent?

Showing the 15 most recent of 17 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.