I think you should provide the source of the results.
Also, I don't agree with the premise that to solve a problem all it needs is a code block and the explanation given is not relevant. I mean we often do just that but understanding why a solution will work or why not is key to learning how to do things in the future without looking them up. Another problem with the lack of comments is that the reader won't notice that a solution is outdated, even though someone noted that on the original StackOverflow page that the snipped originates from.<p>Despite that the project looks very clean and fast for its start and I haven't encountered any technical problems :)
If I am guessing correctly, this is hitting the StackOverflow API and grabbing just the code bits of the answers? The SO upvotes seem to match the star count.<p>Ex:<p>1. <a href="https://justshowmethecode.com/code-example/ruby-on-rails/1k9gy/rails-postgres-drop-error-database-is-being-accessed-by-other-users" rel="nofollow">https://justshowmethecode.com/code-example/ruby-on-rails/1k9...</a><p>2. <a href="https://stackoverflow.com/questions/2369744/rails-postgres-drop-error-database-is-being-accessed-by-other-users" rel="nofollow">https://stackoverflow.com/questions/2369744/rails-postgres-d...</a>
> How many code snippets do you have?<p>> There are more than 33 million code snippets already in our database and more will come.<p>What are the authors of all this code? I presume a lot of code is copyrighted. How do you comply with the license? How can people using this site can comply with it as well?<p>Many free software licenses require attribution, for example.
I clicked one of your first links on the homepage and got this: <a href="https://justshowmethecode.com/browse-code-examples/python%20regex" rel="nofollow">https://justshowmethecode.com/browse-code-examples/python%20...</a><p>I don't know what this is trying to tell me.
The source of the code should be shown. Also, the explanation behind the code is actually usually important in understanding how to fix the problem.<p>I can't say I like this idea of -only- looking at code. Also I don't like the tagline of "Access your required code snippets without thinking". Software engineering is mostly about thinking... not thoughtlessly typing or copy/pasting...
I like this, I would definitely use it. I've been building software for years but there are still things I don't do often enough to remember accurately. In these instances all I want is the code, I don't need the explanation. This makes it very easy to find examples.<p>I agree with the other comments stating that you should include the source of the snippets; include the name of the site and a link back to the original post.<p>It might also be a useful feature to include the accompanying explanation — collapsed, but expandable — for those who would like quick access to it. Of course, if they are that interested I suppose they could just click on the link to the source that you'll be providing :-)