51–60 of 63 posts
Shameless plug: there’s also Debian Code Search at https://codesearch.debian.net/ . It’s based on the same idea as Google Code Search (using regular expressions sped up by a trigram index) and indexes everything that is available in Debian sid. If your search on GitHub isn’t fruitful, consider giving Debian Code Search a spin. Disclaimer: I built it. Happy to answer questions if you have any.
Shameless plug: there’s also Debian Code Search at https://codesearch.debian.net/ . It’s based on the same idea as Google Code Search (using regular expressions sped up by a trigram index) and indexes everything that is available in Debian sid. If your search on GitHub isn’t fruitful, consider giving Debian Code Search a spin. Disclaimer: I built it. Happy to answer questions if you have any.
It shares the biggest problem of Github code search. Duplicate results.
$ curl -s http://ftp.ch.debian.org/debian/dists/sid/main/source/Source... | zgrep '^Package: git$' | wc -l 4
If we didn’t index Debian sid, you’d only get one version per package, but also the results wouldn’t be as fresh.
You can follow one of these two issues: https://github.com/Debian/dcs/issues/40 (at most 1 result per package) https://github.com/Debian/dcs/issues/49 (limit by suite, where you could search something else than Debian sid)
If you have any other ideas about how to address the issue, please let me know.
I wonder how feasible it would be to implement a higher order programming language based on searching code snippets. If it could be made to work, it could potentially speed up development time by an order of magnitude.
It could just as easily turn out to be no better than CASE or rational or any other junk that's come before.
More than a programmer's goldmine, this is Github's. Stack Overflow is trying to become the go-to for sample code and documentation, Github could have a lot to offer in a partnership.
I wonder how feasible it would be to implement a higher order programming language based on searching code snippets. If it could be made to work, it could potentially speed up development time by an order of magnitude.
Order of magnitude? How could anyone possibly know this if it doesn't exist? It could just as easily turn out to be no better than CASE or rational or any other junk that's come before.
This is what I've been using as of late to learn new technologies. I always seem to forget to tell younger developers about using this approach to learn. Something else I would add is that you should try to find well known OSS contributors that work on projects that use tech/languages you use. If you monitor their projects you can pick up great habits from reading through their code.
Sounds like a great approach. Can you (or anyone else) recommend contributors to follow?
Apache Arrow (https://github.com/apache/arrow/) is very interesting and promising project. It is in early state; you can watch the design decisions taken and how they are implemented. Plus it is multi-language project, you can find code in C++, Java and Python.
Earlier quoted context omitted.
And what is the simplification? I can't see it in your git repo
"Percentage: {:.2f}%".format(foobar * 100) vs "Percentage: {:.2%}".format(foobar)
personally, i dislike such spammy prs. it adds nothing to my code, and its not like accepting the pr is going to attract you as a developer on my code.
There was a small lag between repo code and the dump done on Big Query (some days) last time I checked, but it seems that the delay has been getting smaller and smaller over time.
[1] https://cloudplatform.googleblog.com/2016/06/GitHub-on-BigQu...
[2] https://changelog.com/209/
[3] https://cloud.google.com/bigquery/user-defined-functions