Show HN: I got tired of losing great dev resources, so I'm making DevCheatSheets(devcheatsheets.io)
devcheatsheets.io
Show HN: I got tired of losing great dev resources, so I'm making DevCheatSheets
https://www.devcheatsheets.io/
6 comments
Hey folks, I'm Mitch!
I've been a software developer for the better part of a decade now, and I kept running into the same problem:
There are tons of resources for developers out there, but no good way to remember them, share them or discover them.
Over the years I've lost the links to thousands of StackOverflow answers, blog posts, YouTube videos and ChatGPT prompts. This has lead to lost time and tons of headaches trying to track down those golden nuggets.
DevCheatSheets is my solution. It will be both an information repository for developers, as well as a social platform for sharing and contributing to other people's repositories. You'll be able to share, store and discover new resources with other developers and network on your favorite pieces of information.
DevCheatSheets is in its infancy, but you can sign up for the newsletter at the link below.
https://devcheatsheets.io
I've been a software developer for the better part of a decade now, and I kept running into the same problem:
There are tons of resources for developers out there, but no good way to remember them, share them or discover them.
Over the years I've lost the links to thousands of StackOverflow answers, blog posts, YouTube videos and ChatGPT prompts. This has lead to lost time and tons of headaches trying to track down those golden nuggets.
DevCheatSheets is my solution. It will be both an information repository for developers, as well as a social platform for sharing and contributing to other people's repositories. You'll be able to share, store and discover new resources with other developers and network on your favorite pieces of information.
DevCheatSheets is in its infancy, but you can sign up for the newsletter at the link below.
https://devcheatsheets.io
https://news.ycombinator.com/showhn.html
"Off topic: blog posts, sign-up pages, newsletters, lists, and other reading material. Those can't be tried out, so can't be Show HNs. Make a regular submission instead."
"Off topic: blog posts, sign-up pages, newsletters, lists, and other reading material. Those can't be tried out, so can't be Show HNs. Make a regular submission instead."
Constructive criticism: This sounds interesting, but it's lacking tangible examples. What does the interface look like? How do you share things? Are repositories private or open? Are there public repositories for collaboration? I understand the problem you're addressing, but the direction is unclear.
Respectfully, the current webpage and explanation don't provide enough detail to entice me to join the waitlist.
Respectfully, the current webpage and explanation don't provide enough detail to entice me to join the waitlist.
Not trying to entice you with this comment, moreso trying to clarify, especially since you took the time to give constructive criticism:
My thinking is this: everyone has their own repository of useful resources, divided into categories, languages, etc. The public v. private question is a good one: my initial thought is to give users the choice to do public _or_ private. This will let folks create code snippets that they'd rather keep private and share others that they're interested in sharing.
As for collaboration, I think I'd rather divide this up into discussion collaboration (comments, namely, and maybe code-level comments on snippets) and code-level collaboration (like contributing to a piece of code with a Git-like PR), so that users can choose how they want to interact.
I want to re-clarify, this is an idea still in its infancy, so if there's something you'd like to see, that's the real purpose of this post: to get a feel for what folks would like to see, so I'm not just building something for myself.
My thinking is this: everyone has their own repository of useful resources, divided into categories, languages, etc. The public v. private question is a good one: my initial thought is to give users the choice to do public _or_ private. This will let folks create code snippets that they'd rather keep private and share others that they're interested in sharing.
As for collaboration, I think I'd rather divide this up into discussion collaboration (comments, namely, and maybe code-level comments on snippets) and code-level collaboration (like contributing to a piece of code with a Git-like PR), so that users can choose how they want to interact.
I want to re-clarify, this is an idea still in its infancy, so if there's something you'd like to see, that's the real purpose of this post: to get a feel for what folks would like to see, so I'm not just building something for myself.
There's zero info on how the product would work or what it even looks like. I need something more tangible to want to sign up as well.
That's totally fair! This is a project I started last week, so I definitely plan on posting more about it in the future, on the blog, etc. I got some good feedback on Reddit about feature requests, and HN is full of devs who would benefit from something like this, so I wanted to gather some feedback on what people would want.
The problem is, I lose them.
I've talked to a ton of developers, and they all have various ways of partially solving this problem: - Notion documents with messy link dumps - 1,000,000 tabs open constantly - A bookmark folder that takes up half of your disk space
DevCheatSheets is going to solve this by serving as a repository of useful developer resources that you can share with others. You will be able to create code snippets to remember for future projects, GPT prompts that gave you great output and more. You will also be able to discover new resources from other developers that are specific to your focus and chosen languages.
DevCheatSheets is currently in development, but you can visit the site to sign up for a free newsletter to get updates on its development!
https://devcheatsheets.io