HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
cjbarber
ToolsOfTheTrade
OPEN SOURCE2014–2024
cjbarber / ToolsOfTheTrade

ToolsOfTheTrade

Tools of The Trade, from Hacker News.

16Distinct people
28Mentions
0Explicit recommenders
17.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Tools of The Trade, from Hacker News.

GitHub

Where it is used

No documented product use was verified in the last source check.

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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 6:01:32 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 year28 dated mentions

Observed mentions: 2014-07-13 22:14:14 UTC to 2024-09-16 21:13:48 UTC.

0123452014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

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
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC413
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC514
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC211
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC413
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 UTC303
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC303
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC303
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

5 sources
cjbarber·Aug 24, 2015Submission

Ask HN: What are your favorite tools for getting work done?

I have this repo on Github, though it's more of an all inclusive list. https://github.com/cjbarber/ToolsOfTheTrade What I'm really curious about is -- what tools do you love so much that you recommend them to others any chance you get? For me: - Quip. Start using it. It will eliminate any use for Google Docs and Evernote. It's a much faster version of Google Docs. Make sure you download the desktop and mobile apps though, otherwise it's not as good. What tool is so good that you know others will love it once they start using it?
8 points · Open discussion
"Large scale services" is a subjective number. If every request is 'heavy' at the backend the N of N req/s is lower. Lighter static content serving backends have a much higher N. Therefore, the engineering that goes behind optimizing these is different. IMHO, the N is not everything there is to a devOps engineer. In practical experience- a backend service i worked with had just 30 req/s at the front layer servers but generated 60M logs per day. As the logging guy i got to brag about larger Ns, while the front-layer work was more challenging. 1. Your 100 users/min may also be put across as 300 req/min. 2. Try startups that are going from 10 req/s to 100 req/s rather than directly approaching large, massively distributed backends. 3. To seriously qualify for these you also need the skill sets. Experience with centralized logging, multi area
Read the rest
-zone data-centers, deploying at scale, configuration management, advanced version control workflows, deeper understanding of protocols, caching, awareness of security pitfalls, knowledge of GNU/Linux internals etc will certainly help. 4. Even in the absence of much production experience, you can significantly lower their concerns by demonstrating working knowlege in multiple of these above mentioned skill sets. Also, take a look at https://github.com/cjbarber/ToolsOfTheTrade.
In Ask HN: How to get experience deploying large scale services

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.