Show HN: Stack Decisions – see why tools are being chosen
1–10 of 11 posts
Re: Show HN: Stack Decisions – see why tools are being chosen
#2OP 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!
Re: Show HN: Stack Decisions – see why tools are being chosen
#3OP 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 too…
I really like the idea of it if you can get critical mass. One concern I'd have is: given that people's livelihoods are often on the line, how do you keep it from devolving into Quora marketer-speak over time?
Re: Show HN: Stack Decisions – see why tools are being chosen
#4OP 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 too…
I really like the idea of it if you can get critical mass. One concern I'd have is: given that people's livelihoods are often on the line, how do you keep it from devolving into Quora marketer-speak over time?
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.
Re: Show HN: Stack Decisions – see why tools are being chosen
#5I've really been liking Stack Decisions. We have our engineering team write one up whenever they want to make a tech decision (to avoid knee-jerk changes without reason), and it's been great to see what people think of new products we're trying. StackShare itself has been helpful for a while, and decisions adds a ton of context.
Here's an example one we wrote: https://stackshare.io/gkoberger/decisions/101031322441323967
Re: Show HN: Stack Decisions – see why tools are being chosen
#6Your scrolling is broken when the decision modal is open[0]. You should either let the background scroll behind the modal or prevent it entirely.
Re: Show HN: Stack Decisions – see why tools are being chosen
#7There are already too many general and intro postings. Also the postings are not very high density and slow to scan which only works if volume is kept low and focus tight.
Re: Show HN: Stack Decisions – see why tools are being chosen
#8There are already too many general and intro postings. Also the postings are not very high density and slow to scan which only works if volume is kept low and focus tight.
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 :)
Re: Show HN: Stack Decisions – see why tools are being chosen
#9Your scrolling is broken when the decision modal is open[0]. You should either let the background scroll behind the modal or prevent it entirely. [0]: https://i.imgur.com/XYe7pDE.gifv
Thanks for reporting! The team is aware and on it.
Re: Show HN: Stack Decisions – see why tools are being chosen
#10OP 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 too…
It's better than I expected, with C as an option. You seem to be missing everything else I use: assembly, linker scripts, machine code (bare hex opcode bytes).