- Stack Overflow
- Size scale
- Bug reports and feature requests
Linux Kernel Module Cheat: the perfect setup to learn about the Linux kernel, QEMU and gem5
x86 bare metal examples: the best set of x86 bare metal programming examples available on the net
Top-down 2D discrete grid game to develop reinforcement learning for robot / animal like General Game AI agents
Naughty stuff. I like being naughty.
- Stack Overflow Vote Fraud Script. How do you think I got my rep? Just kidding.
- GitHub makes me feel especially naughty:
- All GitHub Commit Emails: I extracted (almost) all Git commit emails from GitHub with Google BigQuery
- A repository with 1 million commits likely the live repo with the most commits as of 2017
- An 100 year GitHub streak, likely longest ever when that existed. It was consuming too much server resources however, which led to GitHub admins manually turning off my contribution history.
Education: a cause I care about. Looked into markup languages and version control for books, before I noticed that this approach was useless and that ranking algorithms are all that matter: free books website.
I have implemented some large features and several smaller improvements.
I consider merged patches there as professional work, since it is the primary product of a profitable startup.
I have started the automated test suite of the project, and coded major features like the
Tocoutline and the header mappings.
I check it from time to time, and make patches when I really need something, because I write in Markdown a lot.
A good language needs a good editor.
Markdown Test Suite: I have implemented the test runner a few months before CommonMark left stealth mode and killed it instantaneously.
Vim: sometimes I got crazy and wasted my time with Vimscript:
Breakthrough Message: aliens!!! Creative / media project, powered by some Python scripts.
I like to answer important questions, for which none of the answers satisfied me, and close duplicates.
I don’t like to refresh the homepage looking for easy rep :-)
Some of the contributions are subjectively self evaluated based on:
How many significant lines changed (no indentation changes, moves, mass refactoring, trivial tests, etc.):
0 only trivial changes 1 < 20 2 < 150 3 > 150
How hard it was to make it. 4 algorithmic lines are harder than 100 web development / documentation lines.
Merged by others
Only patches which were reviewed by at least one person with push permission will be listed here.
This may also include patches which were rejected in favor of another patch, but strongly influenced the merged patch.
Merged by me
Patches which were merged by myself on repositories which I feel have large public visibility, e.g. those to which I have been given push permission.
Repositories to which I gained push permission because of my contributions:
Bug reports and feature requests
- I opened and was confirmed or generated considerable interest
- I wrote comments pointing out a non obvious cause/fix/duplicate.
- I reviewed the patch
This shall not list bugs solved by my accepted pull requests.
Disclaimer: closed source vendors tend to be highly secretive, solving small issues without any reply, so I use my best judgement given the lack of feedback.
The following contributions where not immediately verified by others, but they were not reverted either and I think they are good.
|2014-12||Vim Markdown||Review patch||Add tilde-fenced code blocks|
|2016-05||All GitHub Commit Emails||1||Password disclosure