Non-technical skills were moved to: /#ciro-santillis-skills
I’m not keeping this up-to-date for now as it is too hard to put a number on any skill, and because I haven’t for a job in a while ;-) What really matters are my projects.
|10||You literally have written a book.|
|7 - 9||Expert, go-to person on this technology.|
|5 - 6||Solid daily working knowledge. Highly proficient.|
|3 - 4||Comfortable working with this, have to check manual on some things.|
|1 - 2||Have worked with it previously but either not much, or rusty.|
I copied this grading scale mechanism from a failed Google interview ;-)
One problem with it is that I am always very hesitant to put a 5 on anything, who can not look at the documentation?
It is also hard to scope things right. Who can claim to be a C++ or Linux kernel expert, even if you wrote a book about it, since those are such humongous topics?
As a result, I haven’t updated this in a while, and things may be out of date.
If your project does something that interests me, I can what it takes to contribute. Tell me what I must know, how long I have to learn it, and I’ll call you back when I’ve mastered it.
|4||C / C++||Cheatsheets: C, C++, POSIX C API|
|3||x86 assembly, ELF||Cheatsheet, Paging tutorial, Bare Metal|
|4||Bash||Cheatsheets: language, POSIX / GNU utils|
|4||Java||Cheatsheet, school projects|
|3||Ruby, Rails||GitLab contributions, cheatsheets: Ruby, Rails|
|3||LaTeX, Markdown||LaTeX cheatsheet, Markdown style guide, Markdown Testsuite contributions, Jekyll cheatsheet|
|3||Algorithms||Cheatsheet and implementations|
|3||Linux internals||Linux Kernel Module Cheat|
|4||Buildroot||Some .configs, Linux Kernel Module Cheat uses it a lot|
|3||OpenGL||Cheatsheet and mini projects|
|3||Vim||.vimrc + cheatsheet at end|
|3||Django||Cheatsheet and mini project|
|3||QEMU||QEMU recipes, basic devices|
|1||Chef||For GitLab Contributions|
|1||AWS, Heroku||EC2, SES|
|1||Media formats||Video, Images, FFmpeg|
|1||Networking||Cheatsheet, basic POSIX networking|