Live data from Hacker News

Show HN: Stack Parts - a way to find possible parts for your stack

news.ycombinator.com

11–20 of 49 posts

Re: Show HN: Stack Parts - a way to find possible parts for your stack

#12
Interesting idea. Suggestion: sort the categories at the top by how likely a project is to need/use them. Without getting into religious arguments, I think a fair example would be "language" and "webserver" should sort higher than "graph-store" and "mapreduce".

Also might be a good idea to define the categories for newbies. Most of the categories will need explanation for newbies.

Cool idea, though. I used to use jakarta.apache.org for a similar purpose.

Re: Show HN: Stack Parts - a way to find possible parts for your stack

#15
Awesome! I would love to see a "this is my stack" tool: let people choose parts (maybe in an easy click and drag way) to show their complete stack. With a few stack data points, you could have templates, which users can start with and tweak to show their exact stack.

Re: Show HN: Stack Parts - a way to find possible parts for your stack

#17
One small point - I found it quite hard to read. When I first saw it I assumed it was just some type of tag cloud until I realised that the link on the left is the category.

Also any plans for having it so that I can start with a language, get a list of data-stores that can talk to my chosen language, then get a list of web-servers and so on until I've chosen my stack. Then building on this it would be great if I could get all the API's for the chosen stack!

Thanks for the great little tool!

Re: Show HN: Stack Parts - a way to find possible parts for your stack

#18
post #14

What I would be more interested is interconnectivity between these elements of the stack, which rdbms have an API for the language I have selected for example.

You could load it into Neo4j and generate some connectivity visualizations.

Re: Show HN: Stack Parts - a way to find possible parts for your stack

#20
I maintain something like this personally, in the form of private structured notes, and I know other engineers that do as well. Except we go beyond listing all possible things that can fit into a given category, into instead making quality and suitability judgments about them. What's "best" or the no-brainer/default for a given role, either in the general case or in various special cases. It's a very useful professional technique.

To wit, I generated the following page from my structured notes, and added it to my public website, a few weeks ago:

http://synisma.com/comp_dump/gototech.html

Post reply on HN