I love the idea of a Rotten Tomato approach. Originally, I was just going to have the tools that I've used personally and grade them personally. But I realized how difficult that would be to scale. It could help me to expand my territory in development by adding more skills (example: diving into Ruby, Java or Go and writing articles about tools in in those languages).

Libhunt is massive!! They have so many topics.

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?

Thank you for the insight.

That's actually the goal. "Resources" will provide articles, tutorials, etc. for the tool you pick. You'll be able to filter by open source or commercial, and I will provide screenshots to certain tools (CMSs, Form handlers, etc) where I can.

I get what you're saying about the "No Results Found" and intend to address that. More content will definitely help in that case but given that I got this up and running in under 4 weeks, it's difficult to pool enough to fulfill each filter.

• What was his first project?
• What was the light bulb to know that he would be successful making courses?

Thank you Cody.

I love those ideas. Your initial statement matched well with what Marc recommended me to do during a chat I had with him so I'm going to just do the leg work myself initially. I do think that the achievement system maybe something I consider in the future.