I love the idea of a lib tech coho. I mean, c’mon, it’s so easy to just go through all the motions of an interview, and then get the questions wrong. But, it is so very important to learn the right questions. And, if you don’t ask the right questions, you may never get the right answers.
The question of what to ask is a common challenge for anyone who uses the internet. I know that I find it hard to ask the right questions because I always seem to write the wrong question, or write the wrong question in a way that makes the question sound like it was asked in a different context. But, I am now using the internet to become a better programmer.
If you’ve been following our blog for any length of time you are probably familiar with the term’repo’. A repo is when you fork your project in such a way that you are effectively giving yourself a copy of your project’s full source code and can change it in ways you can’t change it on your own. For example, it might be cool to read the documentation of a project and then be able to change it with a few lines of code.
While it is a great way to learn if you are a coder, repos can be a good way to learn if you are not a coder. The other day I spent an hour searching for documentation of python libraries I’d never heard of. I think I could have done this in about 2 hours on my own. The thing is that a repo is not really just a copy of your code, it also includes version control.
I like that you can copy a repo and then make it the base of a new project. This is very beneficial to teams that want to work together to build something new. Not only is it a great way to learn the code, it’s also a great way to share a repo with others.
Although many people think the way a repo is a repository is to be like a file repository, a repo is a set of files. A repo is not a file repository. You can create a repo from just a single file.
Some time ago I mentioned that I’m not a big fan of version control and so would never use Git. But this is something I’m starting to do more and more now. I’m not really a fan of the idea of “updating” code for anyone else, but I do like a code repository in a way that makes it easy to share with others and that’s a good thing.
The idea of a code repository is to store files. Every file is a unique piece of code that has been placed on a web page. A repository can be anything from a blog to an entire website. This can be done by storing the file in the repository itself, or by storing the file in a central location and then making it available to anybody who needs to access it.
If you think of a code repository as a central location for storing files, then it makes sense. But if you think of a code repository as a centralized location where you can share files with anyone else who can use them, then it makes no sense.
The repository system in lib tech coho is the first in a multi-tiered one. The second tier is the build system. The third tier is the package system. The fourth tier is the tool system. The fifth tier is the documentation system. The sixth tier is the bug-tracking system. The seventh tier is the source-code distribution system. The eighth tier is the build infrastructure.