lisp-koans
git-from-the-bottom-up
lisp-koans | git-from-the-bottom-up | |
---|---|---|
8 | 32 | |
3,067 | 808 | |
0.1% | - | |
0.0 | 0.0 | |
about 1 year ago | about 1 month ago | |
Common Lisp | ||
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
lisp-koans
-
critique my code please?
the koan is here https://github.com/google/lisp-koans/blob/master/koans-solved/scoring-project.lisp (a bit big to also paste here)
- Lisp Koans
-
Hard time moving C-like algorithms to Lisp
Lisp Koans should be safe to endorse, but I honestly haven't run it and it looks like it might need updating.
-
Why these equal hash tables return nil when compared with 'equal'?
I recently found lisp-koans which in my opinion is the best way to learn all the small details of common lisp when used along with hyper-spec. But now I'm stuck at one question
- Are there canonical practice projects for people learning a new language?
-
Free 500+ books and learning resources for every programmer.
Lisp Koans
-
Console 34 includes lisp koans open-sourced by Google that I thought /r/lisp might be interested in :)
Direct link to Github repo, having not a damn thing to do with console.substack.com.
-
Git Koans
https://github.com/google/lisp-koans
git-from-the-bottom-up
- Git from the Bottom Up
-
How Head Works in Git
Here's a great walk through for how Git works from the bottom up: https://jwiegley.github.io/git-from-the-bottom-up/
It's short, easy to understand and you'll understand HEAD.
-
git-appraise – Distributed Code Review for Git
Very tangential:
Gerrit also stores some of its configs in a git repo. I was setting up a new instance, but couldn't get Admin permissions because the way my auth front-end didn't play well with the docker image's assumptions.
Gerrit already does a lot of its work via non-standard references. For example, you don't push to a branch, `refs/branches/foo`, you push to a separate `refs/for/foo` namespace that creates the review.
Similarly, Group config is stored in the All-Users git repo [1], but in references created after a UUID, in `refs/groups/UU/UUID`.
I ended up having a to exercise the plumbiest of plumbing commands [2] to create a new commit from scratch (from a tree, from the index, from blobs), to update the group ref to add myself to the Administrators group (this, of course, requires a local shell and permissions on the Gerrit host). It was a great way to exercise what I had learned in Git from the Bottom Up [3]
[1] https://gerrit-review.googlesource.com/Documentation/config-...
[2] https://git-scm.com/book/en/v2/Git-Internals-Git-Objects
[3] https://jwiegley.github.io/git-from-the-bottom-up/
- Setting up Huginn on Heroku
-
Books for learning Git
I found Git from the Bottom Up helpful. It is very short as well. Then refer to the official book when you want more detail.
- Good git course and/or where to practice real life scenarios?
-
the first time i had to deal with a huge git rebase conflict
I recently came across "Git from the Bottom Up by John Wiegley" (thanks to Coding Blocks podcast), he has a chapter about rebasing: https://jwiegley.github.io/git-from-the-bottom-up/1-Repository/7-branching-and-the-power-of-rebase.html
-
Git-SIM: Visually simulate Git operations in your own repos with a single termi
You won't have to put your entire life on break in order to understand the fundamentals of git and why it works the way it works. Going through https://jwiegley.github.io/git-from-the-bottom-up/ and really understanding the material will take you a couple of hours at max, but will save you a lot of time in the future.
Wanting to understand things before using them is hardly elitism, not sure why you would think that.
Just like you probably don't want to fix bugs without understand the cause, it's hard to use a tool correctly unless you know how the tool works.
- What is the most efficient way of learning and comprehending Git?
What are some alternatives?
react-bits - ✨ React patterns, techniques, tips and tricks ✨
devdocs - API Documentation Browser
guide.elm-lang.org - My book introducing you to Elm!
mark-sweep - A simple mark-sweep garbage collector in C
JavaScript-es6-and-beyond-ebook - A comprehensive, easy-to-follow ebook to learn everything from the basics of JavaScript to ES2020. Read more on my blog https://inspiredwebdev.com or buy it here https://leanpub.com/completeguidetomodernjavascript2020. Get the course here https://www.educative.io/courses/complete-guide-to-modern-javascript?aff=BqmB [Moved to: https://github.com/AlbertoMontalesi/The-complete-guide-to-modern-JavaScript]
git-appraise - Distributed code review system for Git repos
git-fire - :fire: Save Your Code in an Emergency
elasticsearch-definitive-guide - The Definitive Guide to Elasticsearch
emlop - EMerge LOg Parser
Kalman-and-Bayesian-Filters-in-Python - Kalman Filter book using Jupyter Notebook. Focuses on building intuition and experience, not formal proofs. Includes Kalman filters,extended Kalman filters, unscented Kalman filters, particle filters, and more. All exercises include solutions.
tig - Text-mode interface for git