yonasb
Joined 16 years ago
Karma
1,348
Submissions
172
Member since
Oct 27
Recent submissions
Comment · 3 years ago
Great guide. One thing that seems to be missing is something I see in a lot of README's: a list of the core tech stack being used in the repo. Good examples here https://github.com/undb-xyz/undb#-tech-stack and here https://github.com/steven-tey/novel#tech-stack. Did you already consider adding this as part of the guide and decide against it, or was it just not something you thought to add?
Comment · 4 years ago
StackShare | Developer Advocate | Full-time | Remote (US hours)
StackShare (https://stackshare.io/) now has a community of over one million developers sharing their tech stacks and advice on tools & technologies publicly. More recently, we launched our enterprise product called Private StackShare which helps companies automatically map out all the tech stacks they're using via Git integration. Eventually we believe that no developer in the world will make a technology decision without first checking StackShare, to see what others are using inside (private) and outside (public) of their company.
We're hiring a Developer Advocate to engage the community and help us create a brand new category of SaaS: tech stack intelligence. This role is primarily focused on content and community, and you'll be reporting directly to the CEO (me). You’ll have real input into product decisions and help drive product strategy by working closely with the leadership team.
Some Developer Advocate / Developer Evangelist experience is required.
Full details can be found here: https://angel.co/company/stackshare/jobs/1940192-developer-a...
And our tech stack: https://stackshare.io/stackshare/stackshare
Comment · 6 years ago
Hey HN! We’ve been quietly testing a new feature on StackShare over the past year where we let people ask for advice on which tool they should use in a given scenario. Stack Overflow is the best for programming questions, but they don’t allow for opinion-based discussions about which tooling to use for different use cases. HN is great too whenever there happens to be a popular Ask HN thread related to picking tools, but they're pretty infrequent.
So we built a new experience just for getting Stack Advice! To ask for advice all you need to do is describe your situation, your constraints, tag the relevant technologies, and your request gets shared with a network of thousands of developers that have used the tools you're asking about. There are some great discussions happening already, over 1,000 advice threads so far! Would love to hear everyone's feedback :)
Comment · 7 years ago
OP here- we’ve been working on this offering for a while now. The data available on StackShare has always been one of the most interesting aspects of what we’re building. We’ve generally stayed away from offering an API because we weren’t sure how we wanted to offer it and exactly what we wanted to offer. I mentioned this on Product Hunt yesterday- the last thing we wanted to do was open it up as a free service and then have to shut it down once it was time to start monetizing. So we decided to do this sustainably from the start; for the beta, we’re offering the API as a paid service.
The public data you see when browsing stackshare.io is a small fraction of what you get via the new API. We’ve built our own scrapers and crawling infrastructure to figure out the backend technologies companies are using via public sources and combined that with the technology graph we had already built up to create one high quality dataset. We tell you how/where we get all the data that we serve up and we have a lot more backend technologies than most other similar APIs.
We’d love to hear your feedback!
Comment · 8 years ago
Thanks for reporting! The team is aware and on it.
Comment · 8 years ago
Thanks for the feedback! Would love some examples of ones you think are general/intro- we're manually curating to a certain extent so we want to make sure we know which ones the community generally doesn't find useful. The idea is that if you're logged in, you'll see Decisions relevant to your stack.
The posts aren't meant to be high density, so that's intended :)
Comment · 8 years ago
Thanks! I think there will be a similar challenge here, but we have community moderators (as of launch) and pretty strict rules around self-promotion. Example: some vendors (tool makers) wanted to write Decisions about their own product, but we explained why that's not helpful to developers and they understood. In many ways HN is really good at this, so the hope is that we can let the community moderate itself which seems like less of a thing on sites like Quora.
Comment · 8 years ago
OP here- excited to show this to the HN community! Someone posted the intro blog post in another thread but our plan was to just show off the product so here it is! Decisions is a way to quickly explain a specific technology decision you made.
Twitter is great, blog posts are great, but we think there's an interesting medium (pun intended) that could be really helpful when you're trying to make a decision about a tool or putting together a workflow. Example: I like this one about payments because it's pretty descriptive https://stackshare.io/adrienjarthon/decisions/10114566434535....
We believe sharing technology decisions should be as commonplace as writing an organized and thorough README.md. Ultimately, our goal is to increase the net amount of knowledge about technology accessible to all developers, which in turn will help make you more productive at work.
Contributing Decisions gives you visibility amongst other developers who care about the tech you’re talking about, and gives you the opportunity to discuss the technical details associated with that decision.
As I mentioned in the other thread, our hope is that over time, you'll end up with this structured repository of discussions around technology problems/solutions for a wide range of use cases that you can come back to whenever you need help.
More details about the launch here: https://stackshare.io/posts/introducing-stack-decisions.
Would love to answer any questions or hear your feedback!