I'm not sure what problem you're trying to solve. Could you verbalize this?
If it's about helping me find dev tools that solve my problem, you're basically competing with Google and all the other curated collections it can search through (such as the Awesome lists, mentioned by @russ). I really think that's an uphill battle you don't want to fight.
My advice would be to figure out what Google/etc isn't solving for you, and then build a product that addresses that. Right now it feels very unfocused and a bit like "a jack of all trades, master of none" if that makes sense.
One thing Google isn't as good at is discovery. When you don't exactly know what you're searching for.
I think the Awesome lists are good at that, but they aren't necessarily the best interface. If you were to target a specific niche (e.g. "TDD for Ruby" or "Tools for static sites") and do a weekly email etc with new tools/etc I think that might be a better starting point.
A challenge that I've faced several times when starting a new website is finding certain tools. The goal of DevTools Directory is to provide a central location for all development tools with a way to filter by language, type and/or license. There are a few missteps in the current iteration but the core of the idea is there.
The lists that @russ mentioned are new to me and definitely make #dtd kind of obsolete (lol).
You suggest to niche down even further than developers into languages, frameworks, etc?
Yeah I think "developer tools" is very broad. When I looked at the section that's relevant to me (Ruby) I saw only 3 tools, which isn't very compelling. I think it would be very hard to create a collection for dozens of categories. Better to focus on one category first and do it right. Then expand from there.
I'm not sure what problem you're trying to solve. Could you verbalize this?
If it's about helping me find dev tools that solve my problem, you're basically competing with Google and all the other curated collections it can search through (such as the Awesome lists, mentioned by @russ). I really think that's an uphill battle you don't want to fight.
My advice would be to figure out what Google/etc isn't solving for you, and then build a product that addresses that. Right now it feels very unfocused and a bit like "a jack of all trades, master of none" if that makes sense.
One thing Google isn't as good at is discovery. When you don't exactly know what you're searching for.
I think the Awesome lists are good at that, but they aren't necessarily the best interface. If you were to target a specific niche (e.g. "TDD for Ruby" or "Tools for static sites") and do a weekly email etc with new tools/etc I think that might be a better starting point.
A challenge that I've faced several times when starting a new website is finding certain tools. The goal of DevTools Directory is to provide a central location for all development tools with a way to filter by language, type and/or license. There are a few missteps in the current iteration but the core of the idea is there.
The lists that @russ mentioned are new to me and definitely make
#dtd kind of obsolete (lol).
You suggest to niche down even further than developers into languages, frameworks, etc?
Yeah I think "developer tools" is very broad. When I looked at the section that's relevant to me (Ruby) I saw only 3 tools, which isn't very compelling. I think it would be very hard to create a collection for dozens of categories. Better to focus on one category first and do it right. Then expand from there.